|
|
| Line 1: |
Line 1: |
| − | Approved November 9, 2009
| + | See InM web site for [http://www.hl7.org/documentcenter/public/wg/inm/2014-09-16-InM-SWOT.rtf updated SWOT] approved 2014-09-16 |
| | | | |
| − | *Strengths
| + | Return to [[Infrastructure and Messaging]] |
| − | **Very knowledgeable participants
| |
| − | **Well-known and well-used Standards
| |
| − | | |
| − | * Weaknesses
| |
| − | **Lack of regular participation
| |
| − | **Lack of resourcing to work with other groups or new work items
| |
| − | **Scope of WG is narrow
| |
| − | **Need for new standards is not uniform. There are a couple of efforts in other HL7 WGs which will need either modified or new INM standards which have not been resourced. One project needs additional work with batch. Another project(s) are working on services (which will also affect the current INM standards).
| |
| − | | |
| − | * Opportunities
| |
| − | **Wrappers R2 will be a chance to re-engage all interested parties
| |
| − | | |
| − | * Threats
| |
| − | **Limited participation
| |
| − | **Limited Scope
| |
| − | | |
| − | *Discussion points:
| |
| − | * Real focus is message transport over wire.
| |
| − | * Much of the core work has been moved elsewhere.
| |
| − | * We need to answer the model of a SOA sender sending a message where one of the recipients is a repository which receives messages.
| |
| − | * Our responsibility/value added is to ensure that V3 communications will support at a minimum V2 use cases in the newer technologies.
| |
| − | ** We will define and make visible and put on paper the V2 use cases for reference.
| |
| − | ** We will define a “bare socket” implementation.
| |
| − | ** We will evaluate other transport mechanisms to satisfy the use cases.
| |
| − | ** Mark Tucker will help coordinate, as will Larry Reis.
| |
| − | * We need to make sure that the payload will get from the sender to the receiver.
| |
| − | * If blue classes (MCAI/MCCI) are removed, we have yet another form of loosely coupled communication.
| |
| − | * There are few established V3 ‘legacy’ applications. We should ask the community to help expand the set of use cases.
| |
| − | | |
| − | | |
| − | Return to [[Infrastructure and Messaging TC]] | |
