Hi, 1. I would definitely not model my domain objects following the HL7v2 messaging standard. It's really targeted at messaging. HL7v3 goes one or two steps further as it incorporates a framework for developing domain models. At its base there's the Reference Information Model (RIM), which may also be used as foundation of a application-specific domain model. Have a look at http://en.wikipedia.org/wiki/Health_Level_7#HL7_Version_3 or http://www.hl7.org.au/HL7-V3-Resources.htm as a starting point.
2. The HL7 spec is pretty essential I would say, at least for understanding the semantics of the individual HL7 messages, segments, types etc. 3. HL7v2 started off way before XML was "invented". However, here's a equivalent XML encoding of HL7v2 messages, and HAPI provides an XML Parser to parse and render HL7v2 message in XML encoding. 4. The spec title is a bit misleading. It's obviously revision 10 of this endoscopy device specification. Chapter 2 says that it creates and sends messages according to Health Level Seven, Version 2.3. The latest official HL7v2 version is indeed 2.6; 2.7 coming soon. regards Christian Pankaj Tandon wrote: > > Hi all, > I get the feeling that I am in the wrong room (forum) because my questions > are "User" related, not API developer related. However, I could not find a > forum for HAPI users so I thought I'll post my questions here: > > First, I am looking for developing a medical app and I thought that I > would design the domain model of my app in line with the HL7 protocol. But > after looking at the specs, it seems that the spec is purely for > interchange of data, not for the storage of it. But then I read somewhere > in the spec that it was written for a relational database. So I am > confused. Specifically, is it recommended that I model my domain objects > based on this standard? If so, where in the spec can I find pointers for > doing this? > > Secondly, it is really nice that HAPI is out there, but as an app > developer, am I expected to know the HL7 spec, or go purely by the javadoc > and the examples on the project site? > > Thirdly, Why is this spec not in XML. It it just a vestige of how it grew, > or there is a reason why the spec is not a bunch of XML schemas (or even > DTDs) today. > > Lastly, what IS the current version of HL7. I have a link here that says > HL7 version 10 : > http://www.olympus-europa.com/endoscopy/images/HL7_Specification.pdf > Is that the latest? If so, why is the HAPI messages API still at 2.6? Just > not caught up or is it a different version I need to see. > > Thanks in advance and sorry if these questions are misdirected. Please > route appropriately. > > Pankaj > > > > -- View this message in context: http://old.nabble.com/User-level-questions-tp27375231p27459999.html Sent from the hl7api-devel mailing list archive at Nabble.com. ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ Hl7api-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hl7api-devel
