Hi, At first I'd like to appologies to reply the last mail to James' personal mail instead of list. But it's Kmail's bad :) . When we back to topic;
Actually there is nothing so special about validations in IHE profiles. IHE's approach is simple, getting standarts from HL7 and defining some rules on them in technical frameworks. For example here [1] is a small part of the RAD technical framework volume 2. As you will see document below, IHE can define a field ( which is specified optional in HL7 guide ) as conditional or reqired. In a similar way they can do this for segments in a message... As I said in my last message I think conformance profiles will be enough to satisfy IHE's requirments. But the problem is I've to write all profile for all messages and fields again and again. I'd like to figure out, is there a way to override only some of fields for every message which is needed ? PS: May be another solution will be using "Open eHealth Integration Platform" for validations which is based on HAPI and Apache Camel ? [2] [3] [1] https://worksanita.regione.emilia- romagna.it/sites/grts/Materiale_IHE/Transaction%5CRAD_2.pdf [2] http://gforge.openehealth.org/gf/project/ipf/ [3] http://architects.dzone.com/articles/introduction-open-ehealth?page=0,0 On Wednesday 22 July 2009 11:11:19 pm you wrote: > Hi there, > > Hmm, interesting. I haven't personally worked with the IHE radiology > profiles, so I'm not too sure what's involved in implementing them. > > What kind of validations would you need to do for your segments? Can you > provide an example or two? Also, are they captured electonically in any way > (i.e. XML schema or something like that)? I'm thinking it may be possible > for you to do this by extending existing segment classes somehow and then > using a custom ModelClassFactory to provide your own customized > implementations to the parser. > > Cheers, > James > > On Wed, Jul 22, 2009 at 12:56 PM, Serbulent Unsal < > > [email protected]> wrote: > > On Tuesday 21 July 2009 10:27:26 pm you wrote: > > > Hi Serbulent, Erik, > > > > Hi James, > > > > At first thanx for your reply. > > > > > The database in question is not the RIM database, but actually an > > > access database developed by Frank Oemig in Germany. He has a page > > > about it > > > > here: > > > http://oemig.de/HL7/hl7db.htm . I'm not actually sure what is involved > > > > in > > > > > purchasing a copy, but I believe you need to contact HL7 international. > > > > I try to contact them but I couldn't get any reply for now. > > > > > ... > > > If you are trying to create custom message classes, this is > > > actually fairly easy (although not well documented) without the use of > > > a database. If you are trying to do that, maybe I can talk you through > > > it > > > > and > > > > > improve the documentation in the process. > > > > We are trying to implement some IHE actors from radiology domain. So we > > need > > to change some validation rules for segments and messages according to > > IHE framework. > > > > For messages we can use conformance profiles i think, but for segments we > > can't > > figure out what can we do beyond a lots of if...else blocks. > > > > May be we can define rules for segment again and again in every message > > conformance profile but it's too dirty solution like using if..else > > blocks. > > > > So I can't find a good solution at all... > > > > Thanx... > > > > > > > > PS: Is there any predefined rule files for standart HL7 messages that you > > know > > or sould we write them once more to use in our application ??? -- Serbulent Unsal | Software Expert GSM : +90 555 697 50 46 | Tel : +90.312.478 48 00 Akgun Softwares & Services Pvt. Ltd. Çetin Emeç Bulv. 4. Cad. No:5/3 06460 A.Öveçler / ANKARA This e-mail and its attachments are private and confidential to the exclusive use of the individual or entity to whom it is addressed. It may also be legally confidential. Any disclosure, distribution or other dissemination of this message to any third party is strictly prohibited. If you are not the intended recipient, you may not copy, forward, send or use any part of it. If you are not the intended recipient or the person who is responsible to transmit to the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and its attachments. ------------------------------------------------------------------------------ _______________________________________________ Hl7api-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hl7api-devel
