Page History
...
$ wget https://open.med.harvard.edu/svn/shrine/releases/1.18.0/code/broadcaster-aggregator/src/main/resources/hub.sql
$ mysql -u $SHRINE_MYSQL_USER -p$SHRINE_MYSQL_PASSWORD -D shrine_query_history < hub.sql
Shrine.conf Changes
In Shrine 1.18.0+, it is now required to specify the names of result types corresponding to breakdown queries. There names must match the names of result output types defined in the i2b2 DB of every node on your Shrine network. For example, on a network comprised of nodes backed by i2b2 demo VMs, add this to shrine.conf:
shrine {...breakdownResultOutputTypes {PATIENT_AGE_COUNT_XML {description = "Age patient breakdown"}PATIENT_RACE_COUNT_XML {description = "Race patient breakdown"}PATIENT_VITALSTATUS_COUNT_XML {description = "Vital Status patient breakdown"}PATIENT_GENDER_COUNT_XML {description = "Gender patient breakdown"}}...}
...
Since this breakdown result output type information will be shared by many nodes on a network, it's also possible to define it in its own file, breakdowns.conf, which can be shared among sites without revealing URLs or credentials. That file should contain only the enclosing shrine { ... } block and the breakdownResultOutputTypes {... } block, like
shrine {breakdownResultOutputTypes {PATIENT_AGE_COUNT_XML {description = "Age patient breakdown"}PATIENT_RACE_COUNT_XML {description = "Race patient breakdown"}PATIENT_VITALSTATUS_COUNT_XML {description = "Vital Status patient breakdown"}PATIENT_GENDER_COUNT_XML {description = "Gender patient breakdown"}}}
...
If breakdowns.conf is present and no shrine.breakdownResultOutputTypes block is defined in shrine.conf, values from breakdowns.conf will be used.
...
Overview
Content Tools