Go to the first, previous, next, last section, table of contents.

Managing the Results Mapping


LabEventInfoMgr [-cru] files ...
LabEventInfoMgr [-DM]


The LabEventInfoMgr program is the "manager" for the LabEventInfo database. It is used to create the compiled, hashed form of the database from the tabular form or to dump the contents of the compiled form into the tabular form.

An idb script can be generated from the database that when run creates a LabEventMap that is thus always consistent with the LabEventInfo database.


-c files ...
create the database
-r files ...
update the database (update)
-u files ...
update database (insert)
dump database into the tabular form
create idb script for LabEventMap


After updating the file `LabEventInfo.tab' use:

LabEventInfoMgr -c LabEventInfo.tab

to rebuild the compiled database, and then

LabEventInfoMgr -M > LabEventMap.idb

to build an idb script.


The location of the external code databases for LOINC, LabEventInfo and units. This is rarely used, since everyone uses the names compiled into the programs.


the tabular source version
the compiled, hashed file
the run log file used if syslog(3) is not used.


Writing errors to the logfile is not useful, since it is a program that is normally invoked manually by an operator.

The table parser is a bit itchy about end of lines

The generated idb script misses the following three opening lines:

SET ColumnMode;
CLEAR FROM LabEventMap WHERE objectId != NULL;
SELECT objectId INTO OID FROM CISCareUnitCfg WHERE name="060_IOP";

The generated idb script tries to insert the admit observations as LabEvents which will cause idb to exit with an error. Those INSERT statements where mappedPtEvent = "" must be manually deleted from the script.


See `labEventInfo.log', the run log file, if you experience problems.

See Also

section The LabEventInfo Table

Go to the first, previous, next, last section, table of contents.