[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [emergency] EDXL Reference Information Model
Agreed, and thanks, Gary, While I suggested it, I certainly don't want to interrupt our work on the practical specs. I just want to be able to say, on occasion, "Hey, I think this (or that) is a candidate for the RIM, which we can just keep in the background as a more or less permanent work in progress until such time as we think we have learned enough to sum up a v1.0. HL7 v2.0 was a decent messaging spec. However, in their attempt to widen it out to cover everything, while building a RIM from which to do that at the same time, got them wrapped around several axles so that they lost a lot of consistency, logic and common sense. I suspect they ran smack into the same problems with parallel development of interrelated aspects of the overall project that we did. The result is something that will have to be retrofitted to make sense or else be sacrificed and started over from 2.0 at the last point where their work made good sense. I just want to make sure we understand the big difference between a DOM and a RIM, and most of our practical bottom-up work is DOM, and I think we do ourselves a big service by starting from the data dictionary, then doing the DOM. Also I think a RIM is a TC-level task, not an SC-level task. Ciao, Rex At 8:53 AM -0500 2/16/06, Ham, Gary A wrote: >Folks, > >HL7 has a RIM. It took many years to build and was only built AFTER the >basic message set was designed as a way of moving to a more object >oriented view. >Although not advertised as such, the GJXDM is best used as a RIM. It >too has taken a long time to build, and is only now coming to age in any >way. And its limitations are directly related to too much initial >abstraction. Understand that I do not oppose abstraction. I think, >however that starting with a base of concrete needs will give us a >better base to abstract from, rather than trying to immediately >understand the gestalt of it all from the top. > >HL7 was built bottom up from known individual requirements. GJXDM and >the DoD Data model were built top down from abstractions that mapped to >requirements. >I like the former over the latter. If we spend forever on the RIM, we >will not get any useful work done for several years. That said, there >is need for a RIM to keep our work coordinated. I say that we should >continue our course of meeting SPECIFIC message requirements first, and >then refactoring our RIM (and our standards over time) to reflect the >results. A bit more work on the RIM. A LOT more practical product. And >a RIM that has practical value. Lets not forget our focus. > >Respectfully, > >Gary A. Ham >Senior Research Scientist >Battelle Memorial Institute >540-288-5611 (office) >703-869-6241 (cell) >"You would be surprised what you can accomplish when you do not care who >gets the credit." - Harry S. Truman > >-----Original Message----- >From: Rex Brooks [mailto:rexb@starbourne.com] >Sent: Thursday, February 16, 2006 8:34 AM >To: Renato Iannella; Aymond, Patti >Cc: Emergency_Mgt_TC TC >Subject: Re: [emergency] EDXL Reference Information Model > >This is a good formulation. A pure reference model like the SOA-RM >really needs a RIM and/or a Reference Architecture, to make it specific >enough for distinct specifications per domain, such as a healthcare >insurance standard derived and/or extended from the ORCHESTRA framework >below. > >It looks like Renato and I are thinking down very similar tracks on >this. > >Just so you know, if it seems like I develop a case of HL7 on the brain, >it is something I will be dealing with on a regular basis in another >effort in the National Center for Ontological Research (NCOR) Committee >on Ontology for Health Informatics. As both the RM and HAvBED >specifications deal with areas that HL7 overlaps, it is going to come up >here as well, so I just wanted to give you all a brief heads up. > >For those with a simlar interest in Health Informatics, I consider the >releasee of openEHR 1.0 a signal event. > >http://www.openehr.org/ > >I also wanted to let everyone know that I will be absent at next week's >TC meeting, on a plane to Nashville, Tennessee and the Fourth National >Medical Banking Institute, an event held by the Medical Banking Project. > >Ciao, >Rex > > >At 5:14 PM +1000 2/16/06, Renato Iannella wrote: >>On 16 Feb 2006, at 04:00, Aymond, Patti wrote: >> >>>RIM is a new concept (or maybe a new nomenclature) for me. Can you >>>point me to a good source for getting up to speed on this artifact? >> >>Most RIM work is not too consistent, but the idea is to model the >>system/environment at such as level as to capture the core >>entities/classes and relationships. More specific extensions and/or >>instances can then be generated from that. >> >>Reference models can be very detailed, like HL7: >> >> >> <http://www.cihi.ca/cihiweb/en/downloads/infostand_chdm_e_InfoModel.pd >> f> >> >>and also apply to info architectures, like the risk mgt ORCHESTRA >framework: >> >> >><http://www.eu-orchestra.org/docs/Reference%20Model%20for%20the%20ORCHE >>STRA%20Architecture%20RM-OA.pdf> >> >> >>Cheers... Renato Iannella >>National ICT Australia (NICTA) >> >> >> >>----------------------------------------------------------------------- >>--- This email and any attachments may be confidential. They may >>contain legally privileged information or copyright material. You >>should not read, copy, use or disclose them without authorisation. If >>you are not an intended recipient, please contact us at once by return >>email and then delete both messages. We do not accept liability in >>connection with computer virus, data corruption, delay, interruption, >>unauthorised access or unauthorised amendment. This notice should not >>be removed. >> >>--------------------------------------------------------------------- >>To unsubscribe from this mail list, you must leave the OASIS TC that >>generates this mail. You may a link to this group and all your TCs in >>OASIS >>at: >>https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > > >-- >Rex Brooks >President, CEO >Starbourne Communications Design >GeoAddress: 1361-A Addison >Berkeley, CA 94702 >Tel: 510-849-2309 > >--------------------------------------------------------------------- >To unsubscribe from this mail list, you must leave the OASIS TC that >generates this mail. You may a link to this group and all your TCs in >OASIS >at: >https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > > >--------------------------------------------------------------------- >To unsubscribe from this mail list, you must leave the OASIS TC that >generates this mail. You may a link to this group and all your TCs in OASIS >at: >https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php -- Rex Brooks President, CEO Starbourne Communications Design GeoAddress: 1361-A Addison Berkeley, CA 94702 Tel: 510-849-2309
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]