This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "RIMBAA 201009 Minutes"

From HL7Wiki
Jump to navigation Jump to search
Line 1: Line 1:
−
On September 15th an international RIMBAA meeting will be held in Rome, Italy. This is a joint HL7 Italy & RIMBAA WG meeting, with [http://www.hl7italia.it/ HL7 Italy] hosting.
+
[[category:RIMBAA Minutes]]RIMBAA WGM held in Rome on September 15/16 2010, in conjunction with the "HL7 Italy Open Days".
−
This meeting has been designated as an out-of-cycle meeting of the international HL7 RIMBAA working group.
 
−
 
 
−
*'''Date:''' September 16 2010, 09:00-13:00
 
−
*'''Location:''' Rome, Italy (Auditorium Invitalia, via Calabria 46, 00187 Roma)
 
−
*'''Co-chairs:''' Rene Spronk (co-chair of the RIMBAA WG), Andrea Ceiner (HL7 Italy)
 
−
*'''Short URL:''' [http://bit.ly/bAsZKt http://bit.ly/bAsZKt]
 
−
 
 
−
==September 16, 09:00-13:00==
 
−
===Minutes===
 
−
#Rene calls to order at 09:15
 
−
#Open-source Dictionary Manager
 
−
#*Andrea: subset of PHI Technology, provided to HL7 Italy for free (it is also available to any party that wishes to use it). Used to manage OIDs (it replaces the Excel version of the italian OID registries) and VOCs (code systems, value sets...) in 1st instance as a client-server program (where eclipse is the client and mysql is the server). A web application will follow next year for search and retrieve and download.
 
−
#*Model is effectively a subset of the HL7 terminology model. Davide presents the vocabulary and OID management part of the tool.
 
−
#**Rene: question: in/export value sets as defined in Eclipse OHT tools? Davide: not at this point in time. Imports delimited files (CSV), that's the format most commonly used by those that provide HL7 Italy with code systems. CTS II integration has been considered but is not used yet. Andrea: tool is end-user oriented. Source code is available should developers wish to support another format. ISO OID registry format not supported, again CSV.
 
−
#**(Leonardo and Silvano join the meeting)
 
−
#The HL7 "Services for RIMBAA" project
 
−
#*Michael van der Zel: project approved in May2010. SOA WG to lead, RIMBAA sponsors. Michael puts the contents of the proposal on the screen. The scope is not clear, needs further work. Formal status of the project unknown.
 
−
#**(Giorgio joins the meeting)
 
−
#*Related/Additional sources: SAIF, HSSP ("Practical Guide for SOA in Health care, vol 1"), Thomas Ehrl, "SOA and HL7 v3  - HL7 Methodology" (part of v3 ballot publication)
 
−
#*Suggest clarification of the project scope to SOA WG: to develop a strategy (which does not conflict with the ideas as put forward in SAIF) for the development of entity/utility level services on top of a RIM-Based persistence layer.
 
−
#**ACTION: Rene to communicate the proposed clarification of scope to the SOA WG.
 
−
#**(Massimo joins the meeting, Leonardo leaves)
 
−
#Use of RIM based services in the UMCG RIMBAA project (see [http://www.ringholm.de/persist/20100916_RIMBAA_Services_UMCG.pdf http://www.ringholm.de/persist/20100916_RIMBAA_Services_UMCG.pdf] for the presentation)
 
−
#*Michael van de Zel: service = interface, payload, behaviour. Starting point is just "below" the end-user requirements. Functional requirements are top of the iceberg, need to find out the hidden parts, the part below the service. Traceability between functional and service/technology models of key importance. EHR-S FM provides an overview of the functions in an EHR system. InfoStrucure = requirements "below the surface"
 
−
#*UMCG application: KernEPD (Summary of Care record). Based on web, CUI, v3, SNOMED, DCM, EHR-S FM.
 
−
#*Funtional model that matches the UMCG requirements: DC.1.4.1. management of allergies, intolerance and averse reactions. Provides an indication of desired functionality and desired content. Use functions as the basis for the service concept. They sometimes combine multiple functions in one service. Ewout: major differences in granularity of the functional requirements.
 
−
#*From the functions derive a design create a system/architecture design (or one could call it the 'abstract deployment diagram'). All services are stateless.
 
−
#*Payload: DCM Information model related to functional requirements, map to logical model (using Care Record Template). Behaviour: act life cycle (state change).
 
−
#*Conclusions
 
−
#**EHR-S FM IN* Functions are ueful as the basis for services in healthcare.
 
−
#**Use of v3 act state model as the basis for behaviour
 
−
#**Traceability great tool to link Technology to Functionality and Impact
 
−
#CIM-based CRUD Storage (see [http://www.ringholm.de/persist/20100916_RIMBAA_CMET_CRUD_exploration.pptx http://www.ringholm.de/persist/20100916_RIMBAA_CMET_CRUD_exploration.pptx] for powerpoint)
 
−
#*Ewout: CIM is now called SIM, by the way
 
−
#*Ewout: I have experience with 2 RIM-based storage projects. Presentation isn't based on either, this is waht i would do if I had to start today. Will be implemented as a proof of concept.
 
−
#*At UMCN (a current project): chose (for v2 inbound interface): don't map to v3 and use v3 services to store in the database. Chose to build separate v2 services to store.
 
−
#*A generic algorithm should be able to merge object trees into object graphs. Current RMIMs are not designed to Update/replace/delete (at persistence layer) specific child acts (of the focal act) and attributes. Merge algorithms needs to underatsnd the intent of the interaction, hits hidden in the prose of implementation manuals, has to be aware of mapping of models to your EHR-model (add project specific data to ensure that mapped data will comply with business rules prior to persisting).
 
−
#*Map interactions to "service level" CRUD operations. Unit of storage = SIM/LIM, lock/create/read/update/delete as a whole. Explicit references to other data (feels like "identifyable" CMET stereotype). Also is the maximum scope for context conduction (if a big model blocks context conduction, then it's probably a boundary of a SIM/LIM), and serves as the unit for documentation. Only the "root object" is referencable, otherwise the management of references and integrity will become unmanagable. CP-style storage.
 
−
#**Relevant book in this context: "Domain Driven Design", by Eric Evans
 
−
#*How does one find these atomic SIM/LIMs? There is, although not explcietely so, an EHR DMIM. Provides consistency. CMETs quite often too large, need to find smaller parts.
 
−
#**ACTION: Ewout to write a draft cehcklist on methods to find 'small pattern models' to be used in CRUD services, based in part on the book by Eric evans. Determine in how far the methods on the checklist impact the "safety" of the models.
 
−
#**Ewout: '''depending on source''' (relaibaility, business context), objects trees are split into atomic parts
 
−
#**Rene: metadata such as trigger event that object-chunks were based on. Ewout: are preserved.
 
−
#**Rene: same services used by the v2-based frontend? Ewout: yes, map v2 message to v3 chunk services.
 
−
#*To be continued at the WGM in Cambridge.
 
−
#Authentication using RIM model
 
−
#*Not discussed, take up during the meeting in London
 
−
#Various RIMBAA/MDD principles using modules from the PHI Technology product suite (Andrea/Davide)
 
−
#*This wasn't discussed due to a lack of time. See [http://www.ringholm.de/persist/20100916_RIMBAA_phi_MDD.ppt http://www.ringholm.de/persist/20100916_RIMBAA_phi_MDD.ppt] for contents of the scheduled presentation.
 
−
#Motion to adjourn at 13:10
 
−
 
 
  
 
==September 15, 10:00-12:00==
 
==September 15, 10:00-12:00==
 +
{| border="1" cellpadding="2" cellspacing="0" style="background:#f0f0f0;" width="100%"
 +
|-
 +
!width=”35%”|Workgroup
 +
!width="20%"| Date/Time
 +
!width="15%"| Location
 +
!width="30%"| Chair/Scribe
 +
|-
 +
|'''RIMBAA WG'''||2010-09-15, <br/>10:00-12:00||Rome, Italy||C/S: Rene Spronk
 +
|}
 
===Attendee List===
 
===Attendee List===
 
{| border="1" cellpadding="2" cellspacing="0"
 
{| border="1" cellpadding="2" cellspacing="0"
Line 137: Line 95:
  
 
==September 15, 14:00-17:00==
 
==September 15, 14:00-17:00==
 +
{| border="1" cellpadding="2" cellspacing="0" style="background:#f0f0f0;" width="100%"
 +
|-
 +
!width=”35%”|Workgroup
 +
!width="20%"| Date/Time
 +
!width="15%"| Location
 +
!width="30%"| Chair/Scribe
 +
|-
 +
|'''RIMBAA WG'''||2010-09-15, <br/>14:00-17:00||Rome, Italy||C/S: Rene Spronk
 +
|}
 
===Attendee List===
 
===Attendee List===
 
{| border="1" cellpadding="2" cellspacing="0"
 
{| border="1" cellpadding="2" cellspacing="0"
Line 210: Line 177:
 
#Discussion of the [[ ]] issue.
 
#Discussion of the [[ ]] issue.
 
#*(''not part of the minutes, added after the meeting''): the terms we were looking for may actually be OLTP and OLAP, see [http://datawarehouse4u.info/OLTP-vs-OLAP.html] for a brief comparison between these concepts.
 
#*(''not part of the minutes, added after the meeting''): the terms we were looking for may actually be OLTP and OLAP, see [http://datawarehouse4u.info/OLTP-vs-OLAP.html] for a brief comparison between these concepts.
 +
 +
 +
==September 16, 09:00-13:00==
 +
 +
{| border="1" cellpadding="2" cellspacing="0" style="background:#f0f0f0;" width="100%"
 +
|-
 +
!width=”35%”|Workgroup
 +
!width="20%"| Date/Time
 +
!width="15%"| Location
 +
!width="30%"| Chair/Scribe
 +
|-
 +
|'''RIMBAA WG'''||2010-09-16, <br/>09:00-13:00||Rome, Italy||C/S: Rene Spronk
 +
|}
 +
===Minutes===
 +
#Rene calls to order at 09:15
 +
#Open-source Dictionary Manager
 +
#*Andrea: subset of PHI Technology, provided to HL7 Italy for free (it is also available to any party that wishes to use it). Used to manage OIDs (it replaces the Excel version of the italian OID registries) and VOCs (code systems, value sets...) in 1st instance as a client-server program (where eclipse is the client and mysql is the server). A web application will follow next year for search and retrieve and download.
 +
#*Model is effectively a subset of the HL7 terminology model. Davide presents the vocabulary and OID management part of the tool.
 +
#**Rene: question: in/export value sets as defined in Eclipse OHT tools? Davide: not at this point in time. Imports delimited files (CSV), that's the format most commonly used by those that provide HL7 Italy with code systems. CTS II integration has been considered but is not used yet. Andrea: tool is end-user oriented. Source code is available should developers wish to support another format. ISO OID registry format not supported, again CSV.
 +
#**(Leonardo and Silvano join the meeting)
 +
#The HL7 "Services for RIMBAA" project
 +
#*Michael van der Zel: project approved in May2010. SOA WG to lead, RIMBAA sponsors. Michael puts the contents of the proposal on the screen. The scope is not clear, needs further work. Formal status of the project unknown.
 +
#**(Giorgio joins the meeting)
 +
#*Related/Additional sources: SAIF, HSSP ("Practical Guide for SOA in Health care, vol 1"), Thomas Ehrl, "SOA and HL7 v3  - HL7 Methodology" (part of v3 ballot publication)
 +
#*Suggest clarification of the project scope to SOA WG: to develop a strategy (which does not conflict with the ideas as put forward in SAIF) for the development of entity/utility level services on top of a RIM-Based persistence layer.
 +
#**ACTION: Rene to communicate the proposed clarification of scope to the SOA WG.
 +
#**(Massimo joins the meeting, Leonardo leaves)
 +
#Use of RIM based services in the UMCG RIMBAA project (see [http://www.ringholm.de/persist/20100916_RIMBAA_Services_UMCG.pdf http://www.ringholm.de/persist/20100916_RIMBAA_Services_UMCG.pdf] for the presentation)
 +
#*Michael van de Zel: service = interface, payload, behaviour. Starting point is just "below" the end-user requirements. Functional requirements are top of the iceberg, need to find out the hidden parts, the part below the service. Traceability between functional and service/technology models of key importance. EHR-S FM provides an overview of the functions in an EHR system. InfoStrucure = requirements "below the surface"
 +
#*UMCG application: KernEPD (Summary of Care record). Based on web, CUI, v3, SNOMED, DCM, EHR-S FM.
 +
#*Funtional model that matches the UMCG requirements: DC.1.4.1. management of allergies, intolerance and averse reactions. Provides an indication of desired functionality and desired content. Use functions as the basis for the service concept. They sometimes combine multiple functions in one service. Ewout: major differences in granularity of the functional requirements.
 +
#*From the functions derive a design create a system/architecture design (or one could call it the 'abstract deployment diagram'). All services are stateless.
 +
#*Payload: DCM Information model related to functional requirements, map to logical model (using Care Record Template). Behaviour: act life cycle (state change).
 +
#*Conclusions
 +
#**EHR-S FM IN* Functions are ueful as the basis for services in healthcare.
 +
#**Use of v3 act state model as the basis for behaviour
 +
#**Traceability great tool to link Technology to Functionality and Impact
 +
#CIM-based CRUD Storage (see [http://www.ringholm.de/persist/20100916_RIMBAA_CMET_CRUD_exploration.pptx http://www.ringholm.de/persist/20100916_RIMBAA_CMET_CRUD_exploration.pptx] for powerpoint)
 +
#*Ewout: CIM is now called SIM, by the way
 +
#*Ewout: I have experience with 2 RIM-based storage projects. Presentation isn't based on either, this is waht i would do if I had to start today. Will be implemented as a proof of concept.
 +
#*At UMCN (a current project): chose (for v2 inbound interface): don't map to v3 and use v3 services to store in the database. Chose to build separate v2 services to store.
 +
#*A generic algorithm should be able to merge object trees into object graphs. Current RMIMs are not designed to Update/replace/delete (at persistence layer) specific child acts (of the focal act) and attributes. Merge algorithms needs to underatsnd the intent of the interaction, hits hidden in the prose of implementation manuals, has to be aware of mapping of models to your EHR-model (add project specific data to ensure that mapped data will comply with business rules prior to persisting).
 +
#*Map interactions to "service level" CRUD operations. Unit of storage = SIM/LIM, lock/create/read/update/delete as a whole. Explicit references to other data (feels like "identifyable" CMET stereotype). Also is the maximum scope for context conduction (if a big model blocks context conduction, then it's probably a boundary of a SIM/LIM), and serves as the unit for documentation. Only the "root object" is referencable, otherwise the management of references and integrity will become unmanagable. CP-style storage.
 +
#**Relevant book in this context: "Domain Driven Design", by Eric Evans
 +
#*How does one find these atomic SIM/LIMs? There is, although not explcietely so, an EHR DMIM. Provides consistency. CMETs quite often too large, need to find smaller parts.
 +
#**ACTION: Ewout to write a draft cehcklist on methods to find 'small pattern models' to be used in CRUD services, based in part on the book by Eric evans. Determine in how far the methods on the checklist impact the "safety" of the models.
 +
#**Ewout: '''depending on source''' (relaibaility, business context), objects trees are split into atomic parts
 +
#**Rene: metadata such as trigger event that object-chunks were based on. Ewout: are preserved.
 +
#**Rene: same services used by the v2-based frontend? Ewout: yes, map v2 message to v3 chunk services.
 +
#*To be continued at the WGM in Cambridge.
 +
#Authentication using RIM model
 +
#*Not discussed, take up during the meeting in London
 +
#Various RIMBAA/MDD principles using modules from the PHI Technology product suite (Andrea/Davide)
 +
#*This wasn't discussed due to a lack of time. See [http://www.ringholm.de/persist/20100916_RIMBAA_phi_MDD.ppt http://www.ringholm.de/persist/20100916_RIMBAA_phi_MDD.ppt] for contents of the scheduled presentation.
 +
#Motion to adjourn at 13:10

Revision as of 14:15, 16 September 2010

RIMBAA WGM held in Rome on September 15/16 2010, in conjunction with the "HL7 Italy Open Days".

September 15, 10:00-12:00

Workgroup Date/Time Location Chair/Scribe
RIMBAA WG 2010-09-15,
10:00-12:00		 Rome, Italy C/S: Rene Spronk

Attendee List

At Name Affiliation Email Address
  Adri Burggraaff Slotervaartziekenhuis, NL adri.burggraaff@slz.nl
  Andrea Ceiner ItalTBS, IT andrea.ceiner@italtbs.com
  Andy Harris National Institute of Health Research (NIHR), UK  
  Arild Hollas CSAM Health, NO arild.hollas@csamhealth.com
  Bas van Poppel iSoft, NL bas.vpoppel@isofthealth.com
  Bertil Reppen Apertura, NO  
R Davide Magni ItalTBS, IT davide.magni@italtbs.com
R Ewout Kramer Furore, NL e.kramer@furore.nl
  Freek Geerdink Vrumun, NL freek.geerdink@vrumun.nl
  Hans Jonkers Philips, NL hans.jonkers@philips.com
  Henk Enting MGRID, NL  
  Kjetil Sanders CSAM Health, NO Kjetil.Sanders@csamhealth.com
R Massimo Frossi ItalTBS, IT massimo.frossi@italtbs.com
R Michael van der Zel UMCG and Results4care, NL m.van.der.zel@ict.umcg.nl
R Rene Spronk Ringholm, NL rene.spronk@ringholm.com
  Roelof Middeljans UMCG, NL  
R Sara Gaion ItalTBS, IT sara.gaion@italtbs.com
  Tessa van Steijn Nictiz, NL stijn@nictiz.nl
  Tom de Jong NovaPro, NL  
  Tommy Kristiansen CSAM Health, NO tommy.kristiansen@csamhealth.com
  Willem Dijkstra MGRID, NL w.p.dijkstra@mgrid.net
R Yeb Havinga MGRID, NL y.t.havinga@mgrid.net

Minutes

  1. Meeting called to order by Rene at 10:30
  2. Administrative issues
    • Agenda Review/Additions/Changes
      • Approved by general consensus
    • Approval of the Minutes of the previous meeting in Rio
      • MOTION by Ewout/Michael to approve the minutes of the RIMBAA WG of the Rio WGM (5-0-0).
    • Announcements
      • Rene: status update on the v3 implementation book. I decided to first create a one day training with the exact same content as the book; and after the training material doesn't show any major gaps anymore to subsequently write the book. During the creation process of the slides for the v3 implementation training course (for full set of slides, see [1]) it became clear that some areas need more discussion within RIMBAA, notably on the subject of the persistence layer.
        • Michael: what I'm missing is some way/description to bridge the gap between the functional and the technical people. Rene: I would call that "localization" of UV models to a certain context. Davide: people need to be aware of the limits of localization, especially on the use and creation of project specific model extensions. This heavily impacts re-use. During discussion the consensus was that the scope of RIMBAA is already wide enough, we need to stay focused.
      • Rene: Charlie McCay (the TSC chair) noted some overlap between the name of the "Implementation and Conformance WG" and the RIMBAA statement that "we're the HL7 v3 implementers". I've addressed an e-mail to the IC WG suggesting they may have to update their mission statement as well as their name - their main focus is on Conformance. This will probably be taken up during the upcoming Cambridge WGM as well.
    • Formal approval of the outcome of the e-mail vote for FTSD representative
      • MOTION by Davide/Ewout: To find the procedure to elect the RIMBAA FTSD representative by e-mail vote to be acceptable, and to accept/reconfirm its outcome (Tony Julian, with 5 out of 9 votes) as reported by the Tally (Rene Spronk). The outcome has been communicated to HQ on August 24. (5-0-0)
    • Report from the HL7 Rio WGM
      • Not a lot of attendees, no regional (South American) attendees. RIMBAA was able to hold all scheduled sessions - the presentation by Cecil was among the highlights of the meeting.
    • Planning of next meeting
      • Cambridge USA (October 2010)
        • Davide: suggest to add discussion of "JavaSIG2010" to the agenda for this WGM.
        • (Yeb Havinga joins the meeting)
  3. JavaSIG 2010 (Davide)
    • Davide: JavaSIG2010 is a revamped version of the old javaSIG material. ItalTBS is serious considering to make this version available to the open source community.
      • This is a javaBeans version of JavaSIG, creating objects with a bean interface instead of POJOs. Datatypes are currently R1, R2 will be taken into account for next version. Map all datatypes to simple database columns.
      • Added useful production information to the base class used by JavaSIG (RimObject)
    • Yeb: one has to be careful when it comes to the Governance of such an open source product: who will be setting the future direction, and how can one guarantee stability and backwards compatibility? Implementers will need to be assured of these things before they decide to use the tool.
    • Discussion: we need to find a couple more interested parties (at least). Victor Chai (Singapore) is one of them.
      • ACTION: Rene to ask DRV Bund (Germany) to verify if they're interested in using the updated version
      • ACTION: Peter Hendler to contact known users of JavaSIG in the US to ensure they know of the new upcoming version and to allow them to express an interest.
  4. Creation of a Java based HL7 v3 Datatypes R2 library
    • Insert Notes by Ewout
  5. Meeting adjourned at 12:45

September 15, 14:00-17:00

Workgroup Date/Time Location Chair/Scribe
RIMBAA WG 2010-09-15,
14:00-17:00		 Rome, Italy C/S: Rene Spronk

Attendee List

At Name Affiliation Email Address
  Adri Burggraaff Slotervaartziekenhuis, NL adri.burggraaff@slz.nl
  Andrea Ceiner ItalTBS, IT andrea.ceiner@italtbs.com
  Andrea Poli O3 Enterprise, IT poli@o3enterprise.it
  Andy Harris National Institute of Health Research (NIHR), UK  
  Arild Hollas CSAM Health, NO arild.hollas@csamhealth.com
  Bas van Poppel iSoft, NL bas.vpoppel@isofthealth.com
  Bertil Reppen Apertura, NO  
R Davide Magni ItalTBS, IT davide.magni@italtbs.com
R Ewout Kramer Furore, NL e.kramer@furore.nl
  Freek Geerdink Vrumun, NL freek.geerdink@vrumun.nl
R Giuseppe Lapis , IT g.lapis@computer.org
  Hans Jonkers Philips, NL hans.jonkers@philips.com
  Henk Enting MGRID, NL  
  Kjetil Sanders CSAM Health, NO Kjetil.Sanders@csamhealth.com
R Mariarita Minerba Caribec, IT mr.minerba@caribec.it
R Massimo Frossi ItalTBS, IT massimo.frossi@italtbs.com
R Michael van der Zel UMCG and Results4care, NL m.van.der.zel@ict.umcg.nl
R Rene Spronk Ringholm, NL rene.spronk@ringholm.com
R Roberto De Lorenzi , IT r.delorenzi@datasiel.net
  Roelof Middeljans UMCG, NL  
R Sara Gaion ItalTBS, IT sara.gaion@italtbs.com
R Saverio Sabina CNR, IT sabina@ifc.cnr.it
  Tessa van Steijn Nictiz, NL stijn@nictiz.nl
  Tom de Jong NovaPro, NL  
  Tommy Kristiansen CSAM Health, NO tommy.kristiansen@csamhealth.com
  Willem Dijkstra MGRID, NL w.p.dijkstra@mgrid.net
R Yeb Havinga MGRID, NL y.t.havinga@mgrid.net

Minutes

    • This part of the agenda will mostly be about providing an overview of some of the key RIMBAA issues; and allowing (italian) vendors/organizations who have used RIMBAA principles (without necessarily being aware that there is such a thing as RIMBAA) to present their applications and approaches.
  2. Overview of Key RIMBAA Issues
  3. Italian RIMBAA experiences
    1. A RIM Based IHE XDS Registry / Repository, using a RIM based database (Andrea Poli)
      • O3Enterprise about creating an IHE XDS Registry solution based on the RIM instead of an ebXML DB structure. The Repository itself is currently not based on the RIM.
    2. RIM-based implementation of a COPD gold-protocol (Chronic obstructive pulmonary disease) (Saverio Sabina, Mariarita Minerva-CaribelIt)
  4. Discussion of the [[ ]] issue.
    • (not part of the minutes, added after the meeting): the terms we were looking for may actually be OLTP and OLAP, see [2] for a brief comparison between these concepts.


September 16, 09:00-13:00

Workgroup Date/Time Location Chair/Scribe
RIMBAA WG 2010-09-16,
09:00-13:00		 Rome, Italy C/S: Rene Spronk

Minutes

  1. Rene calls to order at 09:15
  2. Open-source Dictionary Manager
    • Andrea: subset of PHI Technology, provided to HL7 Italy for free (it is also available to any party that wishes to use it). Used to manage OIDs (it replaces the Excel version of the italian OID registries) and VOCs (code systems, value sets...) in 1st instance as a client-server program (where eclipse is the client and mysql is the server). A web application will follow next year for search and retrieve and download.
    • Model is effectively a subset of the HL7 terminology model. Davide presents the vocabulary and OID management part of the tool.
      • Rene: question: in/export value sets as defined in Eclipse OHT tools? Davide: not at this point in time. Imports delimited files (CSV), that's the format most commonly used by those that provide HL7 Italy with code systems. CTS II integration has been considered but is not used yet. Andrea: tool is end-user oriented. Source code is available should developers wish to support another format. ISO OID registry format not supported, again CSV.
      • (Leonardo and Silvano join the meeting)
  3. The HL7 "Services for RIMBAA" project
    • Michael van der Zel: project approved in May2010. SOA WG to lead, RIMBAA sponsors. Michael puts the contents of the proposal on the screen. The scope is not clear, needs further work. Formal status of the project unknown.
      • (Giorgio joins the meeting)
    • Related/Additional sources: SAIF, HSSP ("Practical Guide for SOA in Health care, vol 1"), Thomas Ehrl, "SOA and HL7 v3 - HL7 Methodology" (part of v3 ballot publication)
    • Suggest clarification of the project scope to SOA WG: to develop a strategy (which does not conflict with the ideas as put forward in SAIF) for the development of entity/utility level services on top of a RIM-Based persistence layer.
      • ACTION: Rene to communicate the proposed clarification of scope to the SOA WG.
      • (Massimo joins the meeting, Leonardo leaves)
  4. Use of RIM based services in the UMCG RIMBAA project (see http://www.ringholm.de/persist/20100916_RIMBAA_Services_UMCG.pdf for the presentation)
    • Michael van de Zel: service = interface, payload, behaviour. Starting point is just "below" the end-user requirements. Functional requirements are top of the iceberg, need to find out the hidden parts, the part below the service. Traceability between functional and service/technology models of key importance. EHR-S FM provides an overview of the functions in an EHR system. InfoStrucure = requirements "below the surface"
    • UMCG application: KernEPD (Summary of Care record). Based on web, CUI, v3, SNOMED, DCM, EHR-S FM.
    • Funtional model that matches the UMCG requirements: DC.1.4.1. management of allergies, intolerance and averse reactions. Provides an indication of desired functionality and desired content. Use functions as the basis for the service concept. They sometimes combine multiple functions in one service. Ewout: major differences in granularity of the functional requirements.
    • From the functions derive a design create a system/architecture design (or one could call it the 'abstract deployment diagram'). All services are stateless.
    • Payload: DCM Information model related to functional requirements, map to logical model (using Care Record Template). Behaviour: act life cycle (state change).
    • Conclusions
      • EHR-S FM IN* Functions are ueful as the basis for services in healthcare.
      • Use of v3 act state model as the basis for behaviour
      • Traceability great tool to link Technology to Functionality and Impact
  5. CIM-based CRUD Storage (see http://www.ringholm.de/persist/20100916_RIMBAA_CMET_CRUD_exploration.pptx for powerpoint)
    • Ewout: CIM is now called SIM, by the way
    • Ewout: I have experience with 2 RIM-based storage projects. Presentation isn't based on either, this is waht i would do if I had to start today. Will be implemented as a proof of concept.
    • At UMCN (a current project): chose (for v2 inbound interface): don't map to v3 and use v3 services to store in the database. Chose to build separate v2 services to store.
    • A generic algorithm should be able to merge object trees into object graphs. Current RMIMs are not designed to Update/replace/delete (at persistence layer) specific child acts (of the focal act) and attributes. Merge algorithms needs to underatsnd the intent of the interaction, hits hidden in the prose of implementation manuals, has to be aware of mapping of models to your EHR-model (add project specific data to ensure that mapped data will comply with business rules prior to persisting).
    • Map interactions to "service level" CRUD operations. Unit of storage = SIM/LIM, lock/create/read/update/delete as a whole. Explicit references to other data (feels like "identifyable" CMET stereotype). Also is the maximum scope for context conduction (if a big model blocks context conduction, then it's probably a boundary of a SIM/LIM), and serves as the unit for documentation. Only the "root object" is referencable, otherwise the management of references and integrity will become unmanagable. CP-style storage.
      • Relevant book in this context: "Domain Driven Design", by Eric Evans
    • How does one find these atomic SIM/LIMs? There is, although not explcietely so, an EHR DMIM. Provides consistency. CMETs quite often too large, need to find smaller parts.
      • ACTION: Ewout to write a draft cehcklist on methods to find 'small pattern models' to be used in CRUD services, based in part on the book by Eric evans. Determine in how far the methods on the checklist impact the "safety" of the models.
      • Ewout: depending on source (relaibaility, business context), objects trees are split into atomic parts
      • Rene: metadata such as trigger event that object-chunks were based on. Ewout: are preserved.
      • Rene: same services used by the v2-based frontend? Ewout: yes, map v2 message to v3 chunk services.
    • To be continued at the WGM in Cambridge.
  6. Authentication using RIM model
    • Not discussed, take up during the meeting in London
  7. Various RIMBAA/MDD principles using modules from the PHI Technology product suite (Andrea/Davide)
  8. Motion to adjourn at 13:10
Retrieved from "https://wiki.hl7.org/w/index.php?title=RIMBAA_201009_Minutes&oldid=40755"