Date: Fri, 29 Mar 2024 11:37:03 -0400 (EDT) Message-ID: <804733680.972.1711726623413@prodopencatalystconfluence.catalyst> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_971_292099209.1711726623410" ------=_Part_971_292099209.1711726623410 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Specify the names of result types corresponding to breakdown queries in = shrine.conf . Their names must match the names of result output types defin= ed in the i2b2 database of every node on your SHRINE network. Your hub admi= n will supply the right breakdownResultOutputTypes for your network. F= or example, on a network comprised of nodes backed by i2b2 demo VMs, add th= is section to shrine.conf:
shrine { ... =20 breakdownResultOutputTypes { PATIENT_AGE_COUNT_XML { description =3D "Age patient breakdown" } =20 PATIENT_RACE_COUNT_XML { description =3D "Race patient breakdown" } =20 PATIENT_VITALSTATUS_COUNT_XML { description =3D "Vital Status patient breakdown" } =20 PATIENT_GENDER_COUNT_XML { description =3D "Gender patient breakdown" } } =20 ... }
The JSON structure for this section is:
breakdownResultOu= tputTypes { <breakdown-result-output-type-name A> { description =3D <string human-readable-description A> } ... <breakdown-result-output-type-name B> { description =3D <string human-readable-description B> } }
Note that breakdownResultOutputTypes can contain 0 or more child element= s.