This wiki has undergone a migration to Confluence found Here
Difference between revisions of "RIMBAA 200901 WGM Minutes"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) |
|||
| Line 1: | Line 1: | ||
| − | Minutes of the RIMBAA WG from the Orlando WGM (Sept. 2008). See also the [[RIMBAA_200901_WGM_Agenda|published agenda for the Orlando WGM]]. | + | Minutes of the RIMBAA WG from the Orlando WGM (Sept. 2008). See also the [[RIMBAA_200901_WGM_Agenda|published agenda for the Orlando WGM]] as well as [[media:2009-01-12 RIMBAA DiscussionSubjects.pdf|presentation with discussion items for Monday.]] |
==Monday Q3 (13:45-15:00)== | ==Monday Q3 (13:45-15:00)== | ||
| Line 20: | Line 20: | ||
===Approval of Minutes=== | ===Approval of Minutes=== | ||
| − | *Approval of the minutes of the last WGM, available at [[RIMBAA 200809 WGM Minutes]] | + | *Approval of the minutes of the last WGM, available at [[RIMBAA 200809 WGM Minutes]] and on the HL7.org website. |
**Approved without objection, 10-0-6. | **Approved without objection, 10-0-6. | ||
| Line 28: | Line 28: | ||
*Dale comments on the persistence layer. Must we also address XML Databases? Should "Query" be added to the Matrix? | *Dale comments on the persistence layer. Must we also address XML Databases? Should "Query" be added to the Matrix? | ||
*Hugh talks about there being a "third dimension" (needs follow up from Hugh) | *Hugh talks about there being a "third dimension" (needs follow up from Hugh) | ||
| − | |||
*Dale: applications have more of a focus on the static model, not on the functional model | *Dale: applications have more of a focus on the static model, not on the functional model | ||
*We focus on Patterns for Application Development. | *We focus on Patterns for Application Development. | ||
| Line 34: | Line 33: | ||
*Technology Matrix is helpfull to understand were you are. | *Technology Matrix is helpfull to understand were you are. | ||
| − | ===Possible candidates for the Tech Matrix=== | + | ===RIM Conformance=== |
| − | *iSoft | + | *Dale: what does it mean to be "RIM compliant", do we need/want to define that? Conformance aspect not at the top of the to-do list for the RIMBAA WG. |
| − | *Eclipse Message Instance Editor + a presistance layer? | + | *Alex DeJong: conformance is related to the "externally observable behaviours", i.e. interfaces. |
| + | *RIMBAA WG doesn't want to make normative statements about application architecture. | ||
| + | |||
| + | ===Possible additional candidates for the Tech Matrix=== | ||
| + | *Need to add/improve descriptions of the approaches taken by RIMBAA implementations | ||
| + | **add: iSoft | ||
| + | **add: Eclipse Message Instance Editor + a presistance layer? | ||
===RS XML-ITS=== | ===RS XML-ITS=== | ||
*There is an interest in the creation of an RS XML-ITS. Grahame/Michael van der Zel | *There is an interest in the creation of an RS XML-ITS. Grahame/Michael van der Zel | ||
*RS/MS cell transition - what's the difference between RS and MS? RS - self discoverable "blob" of RIM based object instances. Theoretically MS is a subset of RS. There are implementation that (wrongly) associate smenatics with clone names, so semantics get lost when transfroming from MS to RS. Current ITS permits MS. | *RS/MS cell transition - what's the difference between RS and MS? RS - self discoverable "blob" of RIM based object instances. Theoretically MS is a subset of RS. There are implementation that (wrongly) associate smenatics with clone names, so semantics get lost when transfroming from MS to RS. Current ITS permits MS. | ||
| − | *RS is more generic. In RS the classCode, typeCode, etc are required. The current MS ITS does not have this requirement. With MS you will have to agree and understand it per interaction. RS has no clone names, just RIM names. In the current reality the clone name is significant. Not all Observations are coded correctly. E.g. bloodpressure morning, afternoon. I would use a different code for them, but currently the Clone Classes get different names so they are semanticly significant and the code of both Observations will be bloodpressure. In the ideal world MS and RS are interchangeble. | + | *RS is more generic. In RS the classCode, typeCode, etc are required. The current MS ITS does not have this requirement. With MS you will have to agree and understand it per interaction. RS has no clone names, just RIM names. In the current reality the clone name is significant. Not all Observations are coded correctly. E.g. bloodpressure with clone name morning, afternoon. I would use a different code for them, but currently the Clone Classes get different names so they are semanticly significant and the code of both Observations will be bloodpressure. In the ideal world MS and RS are interchangeble. |
*RS <-> MS cell transition is MIF based. | *RS <-> MS cell transition is MIF based. | ||
| Line 50: | Line 55: | ||
===Reference Implementation=== | ===Reference Implementation=== | ||
| − | * | + | *Hugh: two options: maximum reference implementation would need to show "all complexity of a real implementation". At a minunimum: pieces that illustrate parts (the various cell-transitions) in the technology matrix. |
*John: how about RIMBAA as a testing framework? Would seem to be a very good application of RIMBAA. | *John: how about RIMBAA as a testing framework? Would seem to be a very good application of RIMBAA. | ||
*Rene: Enhance current Java SIG work with CTS, user interfaces, and a module for the use/migration of legacy data? | *Rene: Enhance current Java SIG work with CTS, user interfaces, and a module for the use/migration of legacy data? | ||
===Cell transitions=== | ===Cell transitions=== | ||
| − | *Guidance how to get from 1 box to another. Start with one path? | + | *Guidance how to get from 1 box to another. Start with one path? Michael vdZ: I'd like to also have legacy addressed. So you at least have some data in the system. How do you deal with legacy systems, is one of the questions you want answered. |
*Maybe an entire path too much work. We should possibly focus on single transitions between cells. | *Maybe an entire path too much work. We should possibly focus on single transitions between cells. | ||
*Examples should be Open Source. | *Examples should be Open Source. | ||
| Line 67: | Line 72: | ||
===SOA CIM/CDA R3=== | ===SOA CIM/CDA R3=== | ||
| − | *Struc Doc is working on a CDA R3 planned for september 2009 with updated Clinical Statement and R2 datatypes. | + | *Struc Doc is working on a CDA R3 planned for september 2009 with updated Clinical Statement and R2 datatypes. This means that there will be one unified Clinical Statement model, and the re-use of templates accross interoperability paradigms. |
| − | |||
==Monday Q4 (15:30-17:00)== | ==Monday Q4 (15:30-17:00)== | ||
| Line 85: | Line 89: | ||
| − | ==Future Goals for RIMBAA WG== | + | ==Future Goals/Workitems for RIMBAA WG== |
| − | *Marketing - Public exposure of successes | + | *Marketing - Public exposure of successes (of v3 implementations and thye RIM itself) |
*Sharing of experiences and solutions | *Sharing of experiences and solutions | ||
*Education - for newbies to RIMBAA | *Education - for newbies to RIMBAA | ||
| − | * | + | *We focus on Patterns for Application Development. Guidance, no normative outcomes. |
| + | *Work with ITS WG on an RS XML ITS and the identification of MS-RS transition issues | ||
| + | *Document/describe (for all possible cell transations) how those steps could be supported/achieved. | ||
Revision as of 11:02, 13 January 2009
Minutes of the RIMBAA WG from the Orlando WGM (Sept. 2008). See also the published agenda for the Orlando WGM as well as presentation with discussion items for Monday.
Contents
Monday Q3 (13:45-15:00)
- Chair (interim, on behalf of Peter Hendler): Rene Spronk, scribe: Michael van der Zel
- Attendees:
- Amnon Shabo, IBM (Israel)
- Mary Desisto, IBM
- John McKim, conmsultant
- Paul J Bayes, Booz Allen Hamilton
- Alex de Jong, Siemens
- Ian Townend, NHS
- Rik Smithies, NHS (UK)
- John Koisch, NCI
- Amit Popat, Epic
- Ilkon Kim, KNU Korea
- Andy Stechischin, consultant
- Grahame Grieve, Kestral
- Russ Sarbora, City of Hope
- Hugh Glover, Bluewave Informatics (UK)
Approval of Minutes
- Approval of the minutes of the last WGM, available at RIMBAA 200809 WGM Minutes and on the HL7.org website.
- Approved without objection, 10-0-6.
Presentation of RIMBAA
- "To RIMBAA is easier than to rumba." ;-)
- Rene provides an overview of "where we are" with RIMBAA. The presentation includes an introduction of the Technology Matrix.
- Dale comments on the persistence layer. Must we also address XML Databases? Should "Query" be added to the Matrix?
- Hugh talks about there being a "third dimension" (needs follow up from Hugh)
- Dale: applications have more of a focus on the static model, not on the functional model
- We focus on Patterns for Application Development.
- Some discussion if the user interface should be under all cells or just the *O and *S columns.
- Technology Matrix is helpfull to understand were you are.
RIM Conformance
- Dale: what does it mean to be "RIM compliant", do we need/want to define that? Conformance aspect not at the top of the to-do list for the RIMBAA WG.
- Alex DeJong: conformance is related to the "externally observable behaviours", i.e. interfaces.
- RIMBAA WG doesn't want to make normative statements about application architecture.
Possible additional candidates for the Tech Matrix
- Need to add/improve descriptions of the approaches taken by RIMBAA implementations
- add: iSoft
- add: Eclipse Message Instance Editor + a presistance layer?
RS XML-ITS
- There is an interest in the creation of an RS XML-ITS. Grahame/Michael van der Zel
- RS/MS cell transition - what's the difference between RS and MS? RS - self discoverable "blob" of RIM based object instances. Theoretically MS is a subset of RS. There are implementation that (wrongly) associate smenatics with clone names, so semantics get lost when transfroming from MS to RS. Current ITS permits MS.
- RS is more generic. In RS the classCode, typeCode, etc are required. The current MS ITS does not have this requirement. With MS you will have to agree and understand it per interaction. RS has no clone names, just RIM names. In the current reality the clone name is significant. Not all Observations are coded correctly. E.g. bloodpressure with clone name morning, afternoon. I would use a different code for them, but currently the Clone Classes get different names so they are semanticly significant and the code of both Observations will be bloodpressure. In the ideal world MS and RS are interchangeble.
- RS <-> MS cell transition is MIF based.
RIM orientation
- RIM was created with an "interoperability mindset".
- Grahame uses the example of the CD datatype - if one were to create the CD datatype with appkication development / persistence in mind it would look totally differently.
- Grahame would also like much mmore normalizations, to re-use communalities between models.
Reference Implementation
- Hugh: two options: maximum reference implementation would need to show "all complexity of a real implementation". At a minunimum: pieces that illustrate parts (the various cell-transitions) in the technology matrix.
- John: how about RIMBAA as a testing framework? Would seem to be a very good application of RIMBAA.
- Rene: Enhance current Java SIG work with CTS, user interfaces, and a module for the use/migration of legacy data?
Cell transitions
- Guidance how to get from 1 box to another. Start with one path? Michael vdZ: I'd like to also have legacy addressed. So you at least have some data in the system. How do you deal with legacy systems, is one of the questions you want answered.
- Maybe an entire path too much work. We should possibly focus on single transitions between cells.
- Examples should be Open Source.
- TASK: Document/describe (for all possible cell transations) how those steps could be supported/achieved. Some of them may have reference implementations (or parts thereof) associated with them to illustrate the principle. And find volunteers to provider detailed descriptions and examples.
Database with native ISO datatypes
- It would be great to have an Ad Hoc query and don't bother with the details of e.g. a PQ.
- Graham has tried to implement UDT's in SQL-Server, but he did not like it because the data is stored serialized as strings.
- Performance is an issue.
- There might be a problem with current ORM implementations witch cannot currently handle UDT's.
SOA CIM/CDA R3
- Struc Doc is working on a CDA R3 planned for september 2009 with updated Clinical Statement and R2 datatypes. This means that there will be one unified Clinical Statement model, and the re-use of templates accross interoperability paradigms.
Monday Q4 (15:30-17:00)
- Chair (interim, on behalf of Peter Hendler): Rene Spronk, scribe: Michael van der Zel
- Attendees:
- Amnon Shabo, IBM (Israel)
- Mary Desisto, IBM
- Paul J Bayes, Booz Allen Hamilton
- Rik Smithies, NHS (UK)
- Amit Popat, Epic
- Hugh Glover, Bluewave Informatics (UK)
- The minutes from this quarter have been included in the documentation of the discussion of Q3 (see above).
Monday Q6 (19:30-21:00)
Future Goals/Workitems for RIMBAA WG
- Marketing - Public exposure of successes (of v3 implementations and thye RIM itself)
- Sharing of experiences and solutions
- Education - for newbies to RIMBAA
- We focus on Patterns for Application Development. Guidance, no normative outcomes.
- Work with ITS WG on an RS XML ITS and the identification of MS-RS transition issues
- Document/describe (for all possible cell transations) how those steps could be supported/achieved.
