Features

Highly granular language for rules specification Processes doses by antigen dose, not administered dose ( see additional details ) Ability to associate identifier with each dose to match input with output (v1.6) Tool for maintaining rules locally without programming Easy reconfiguration of rules by preloading an XML configuration file Web-based testing tool for regression testing Web Service interface with XML payload Adult as well as childhood vaccines Installations in multiple jurisictions Our Difference On the CDC web site is a diagram showing the reccommended vaccine schedule for children.  Many implementations of vaccine forecast begin by processing a history of administered doses, and recommending the next vaccine in this summary schedule. There are several problems with this approach, and MatchMerge solves them:  Challenge MatchMerge Solution The summary schedule only applies to the case of an idealized child.   Real-world cases are more complex; they take myriad paths down through the details and exceptions covered in "pink book".  MatchMerge uses a very granular rules language to accommodate the more complex approach required to model the "pink book" rules. Administered shots may immunize against more than one disease.  For forecasting, vaccine history needs to be considered in terms of doses toward a particular immunity.  MatchMerge uses the approach of breaking "shots" into "zero or more doses". HL7 Version 2 did not assign identifiers to each administered dose.  This created problems in updating immunization histories in a database on an individual shot basis.  HL7 Version 3 does assign an identifier.  MatchMerge optionally allows an identifier to be assigned to each input dose.  This allows validated output to be matched with input with certainty.

 

< Prev		Next >