Is Tolven a Healthcare Integration Engine?
It was not our intent to simply develop a Healthcare Integration Engine, but Tolven does have some of the attributes of an integration engine. Two examples should help explain. First, when a rule processes a new document, it can use information gleaned from that structured document/message to populate other data structures useful for efficient display by end-user applications; however, a rule can also create new documents (or messages). The rule can use information it gleans from the original document as well as other information in the database. Tolven’s architecture allows one message format, say an HL7 V2 message, to be “transformed” to a RIM-based format (or any other format). In so doing, the transformed message is then subject to the same rules as if the message had arrived originally in that format. The second example explains why Tolven works this way. In healthcare, it is often the case that one-to-one transformations between formats are difficult or impossible. Let’s say you
