Flywheel captures data directly MR scanners via its reaper technology. As the scanner produces DICOM data, it is automatically reaped into Flywheel. The images begin appearing in Flywheel within minutes of each acquisition ending. For a typical MR session, the first images will already be in Flywheel before the session has ended!
The Flywheel reaper determines where to place data in the hierarchy using information either entered into the MR console by the user or obtained from the DICOM data. Flywheel uses these 5 pieces of information:
The first three are set by the user into a "Flywheel sort string". This string is entered into an agreed-upon field on the scanner console. Typical fields for the sort string are the Patient ID or the Additional Info. These fields are configurable per site, so you should check with your local Site Admin to confirm the exact location.
Flywheel Sort String has the following format:
Siemens Console Example
At most sites all of the data are automatically reaped into Flywheel. A few sites allow each user to decide whether or not their data is captured by the Flywheel reaper (opt-out or opt-in). An opt-out string of no-flywheel entered into an agreed-upon field, such as the Accession Number, is sometimes configured for sites. If a site has an opt-in policy, entering flywheel can be configured as shown above. Check with your local Site Admin for your site's policies.
Exact integration points, determined during installation, are site- and modality-vendor-specific. In case of incorrect or mistyped Flywheel Sort Info, Flywheel will still receive your data. A user with Site Management privileges will need to toggle into Site Manager mode and assign the Session to the appropriate Project and edit the Subject Code.
Each DICOM modality must be configured with a DICOM destination that points to the Flywheel server and is enabled for DICOM C-MOVE. The default AE Title for Flywheel is flywheel. Detailed instructions for GE and Siemens modalities are available. We are willing to work with other manufacturers, such as Phillips, but system integration and validation will be required.