How does Tolven store and process RIM-based messages and documents?
HL7 has dozens of RIM-based message definitions. Each message definition imposes domain-specific semantic constraints through prose or GELLO and syntax via XML XSDs. All of these domain-specific messages are based on the RIM, which unifies the syntax across domains. From an implementation perspective, it would be prohibitively expensive and time consuming to deal with each of these domain-specific message types independently. Creating rules to process dozens, perhaps hundreds of different messages in different circumstances for different application purposes quickly would get out of hand. Some level of abstraction is needed. Fortunately, in the case of HL7, abstraction of all these messages is not only possible, it is easy: Since all messages are based from the RIM, that is the abstracted model; there is, though, no RIM-level XML representation. So Tolven created one. This is not a new model. It is a RIM-based XML syntax, largely identical to the domain-specific XSDs that provides a si
