This wiki has undergone a migration to Confluence found Here
Difference between revisions of "RIMBAA 201010 Cambridge Minutes"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) |
||
Line 33: | Line 33: | ||
**During the August 2010 harmonization meeting a new 'isCriterionInd' attribute was introduced in all Acts (it replaces all existing CRT moods). See [http://www.hl7.org/documentcenter/public/harmonization/2010Aug/final%5C2010Aug_HARM_FINALPROPOSAL_RIM_MNM_canada_5_RIM%20C00-06%20Fix%20criterion%20stuff_20100722200116.doc] for details of the proposal. | **During the August 2010 harmonization meeting a new 'isCriterionInd' attribute was introduced in all Acts (it replaces all existing CRT moods). See [http://www.hl7.org/documentcenter/public/harmonization/2010Aug/final%5C2010Aug_HARM_FINALPROPOSAL_RIM_MNM_canada_5_RIM%20C00-06%20Fix%20criterion%20stuff_20100722200116.doc] for details of the proposal. | ||
**The new attribute can be used to construct Query-By-Example (QBE) queries. | **The new attribute can be used to construct Query-By-Example (QBE) queries. | ||
− | **Jean will inform us about a) this new mechanism, and b) implementation experiences working with these queries in an SOA v3 [RIMBAA] environment. | + | **Jean will inform us about a) this new mechanism, and b) implementation experiences working with these queries in an SOA v3 [RIMBAA] environment. |
+ | *Use of CMET-like CRUD entity services in the Nijmegen University Hospital (the Netherlands). (Ewout Kramer, Furore) | ||
+ | **Ewout: I construct them by comparing domains and then figuring out how to split the domains into manageable entities. These entities are small, and I also use a kind of reference indicator so one entity can refer to another entity. Large interactions are thus split-up (decomposed) into smaller, independent crud entities that are stored separately and can only reference each other. This way I try to solve the [[Object nets and object trees|Object nets versus object trees]] storage issues. It also makes the store much more approachable and documentable for developers new to v3, I hope. I am storing each entity as a unit in its XML form in an eXist XML database. Splitting transactions and reconstructing them is done using XQuery. | ||
==Thursday Q4 (15:30-17:00) [[Image:Technical med.gif]]== | ==Thursday Q4 (15:30-17:00) [[Image:Technical med.gif]]== |
Revision as of 04:37, 27 August 2010
- Focus this WGM: If one has an RIM based object store, what services should one define? And how does one query it? - RIMBAA will be duscussing ideas and experiences.
- Short URL: http://hl7.me/ro
Contents
Monday Q4 (15:30-17:00)
- Approval of agenda for the week (5 minutes)
- Administrative agenda items
- Agenda Review/Additions/Changes (max 5 minutes)
- Approval of the Minutes of the previous meeting in Rome: (max 5 minutes)
- Announcements
- NOTE: one quarter will be exclusively reserved to discuss RIMBAA issues.
- Canada Health Infoway have a fall partnership conference on November 15-17. This meeting contains presentations on RIMBAA topics, as well as a v3 implementation tutorial. Lloyd McKenzie, Lorraine Constable and Andy Stechishin will be in attendance, and have indicated they'll provide feedback to RIMBAA.
- Report from the Rome WGM (Rene, max 15 minutes)
- Planning of next meeting
- London UK (November 2010)
- Discussion on organizing a RIMBAA meeting in the US between the January and May WGMs.
- Ann Wrightson (SOA co-chair)
- Update on the joint SOA/RIMBAA Services for RIMBAA project.
- Rene Spronk (RIMBAA co-chair)
- Michael van der Zel
- "Simple Store", Template based CRUD Services (Create/Read/Update/Delete, basic services) approach, one Service Decomposition in RIMBAA Applications pattern
Tuesday Q6 (19:00-21:00)
- Focus: this quarter focuses on SOA v3 implementation experiences
- Implementing hData (Gerald Beuchelt, Mitre)
- Presentation on the topic of "mapping hData to in-memory RIM-based object structures" (the CS-CO or CS-RO cell transition in the technology matrix). The presentation will focus on the implementation of hData - and not on an explanation of hData itself.
- hData is (using HL7 speak) a new XML ITS. See HData for an introduction, and www.projecthdata.org/ for detailed specifications, schema and FAQ.
- How does this ITS compare to other ITSs when it comes to issues like code generation, code re-use and content validation?
- Query-By-Example (Jean-Henri Duteau, GP Informatics)
- During the August 2010 harmonization meeting a new 'isCriterionInd' attribute was introduced in all Acts (it replaces all existing CRT moods). See [1] for details of the proposal.
- The new attribute can be used to construct Query-By-Example (QBE) queries.
- Jean will inform us about a) this new mechanism, and b) implementation experiences working with these queries in an SOA v3 [RIMBAA] environment.
- Use of CMET-like CRUD entity services in the Nijmegen University Hospital (the Netherlands). (Ewout Kramer, Furore)
- Ewout: I construct them by comparing domains and then figuring out how to split the domains into manageable entities. These entities are small, and I also use a kind of reference indicator so one entity can refer to another entity. Large interactions are thus split-up (decomposed) into smaller, independent crud entities that are stored separately and can only reference each other. This way I try to solve the Object nets versus object trees storage issues. It also makes the store much more approachable and documentable for developers new to v3, I hope. I am storing each entity as a unit in its XML form in an eXist XML database. Splitting transactions and reconstructing them is done using XQuery.
Thursday Q4 (15:30-17:00)
- Focus: this quarter focuses on open RIMBAA issues, notably those related to the persistent storage of RIM-based models.
- See modules S760, S780 and S785 of the RIMBAA best practices training available at www.ringholm.de/download/HL7v3_implementation.zip
- See these issues on the wiki: Implementation aspects of RIM based database models, ORM best practices.
Friday Q1 (09:00-10:30)
- Focus: Wrap-up, methodology issues surfaced by RIMBAA implementations