Setting Up Idaho Autopsy Results on Your Workstation
The Idaho Autopsy Results program is a forensic documentation and case-management tool that helps pathologists and medical examiners organize, analyze, and report autopsy findings. It streams data from digital imaging systems, links lab results to individual cases, and generates standardized reports that comply with state and federal documentation requirements. Most people try to install it straight from the disc image and then immediately hit a licensing snag. Don't skip the prerequisite check. Start by grabbing the latest build from the official distribution site. The installer is around 840MB, and you will need about 2GB of free space for the database layer plus any DICOM image cache. Run the setup as administrator. During installation, you will be prompted to select a data directory. This is important. I learned this the hard way on a job in Boise where the default C: drive ran out of space mid-implementation because the pathology lab had been storing digitized whole-slide images and CT volumes there for years. I moved the data directory to a secondary NVMe SSD before creating any cases, and the system has been stable since. After the installer finishes, launch the program and go to Administration > Licensing. You need either a network license server or a standalone dongle key. If you are running this on a single machine in a small office, the standalone key is simpler. The network server setup involves configuring a floating license daemon, which takes another twenty minutes but saves money if you have five or more workstations. Once licensed, you will see the main case-entry screen.
Configuring the Database and Imaging Pipeline
The first real configuration step is linking the system to your hospital or county's laboratory information system. Idaho Autopsy Results supports HL7 v2.5 message parsing for inbound lab orders and outbound result feeds. The integration wizard walks you through MLLP socket connections, but it does not handle custom field mapping automatically. You will need to manually assign which HL7 fields map to autopsy fields like cause of death, manner of death, and toxicology flags. Take the time to do this correctly. A misconfigured ALO segment once sent me a case where every toxicology screen defaulted to the previous patient's identity, which required a full audit log review to catch before the report went out. For imaging, the system natively reads DICOM RT structures and standard CT/MRI series. It also has a built-in JPEG 2000 viewer that handles Hologic and Philips digital slide exports without needing third-party plugins. However, older Zeiss Axiocam files from the early 2010s require a manual conversion step using their own export tool before Idaho Autopsy Results can index them properly. Plan for that conversion bottleneck if your archive includes legacy whole-slide images. It usually adds about four to six hours of prep work per thousand cases.
Running a Typical Case Workflow
Creating a new case starts with the patient demographics panel. The system auto-fills date of birth and medical record number from HL7 orders if the LIS connection is active. You then move to the external exam section, which has dropdown fields for wound descriptions, ligature marks, and other visible findings. The documentation is more rigid than older paper-based systems, which can feel constraining at first. I have found that setting up a custom terminology library for your office's most common findings cuts documentation time from about twelve minutes per case down to roughly five. Internal examination follows a structured organ-by-organ workflow. Each organ has predefined measurement fields, weight inputs, and narrative text boxes. The software enforces required fields before you can close a case section, which prevents the accidental submission of incomplete reports. Toxicology results appear in a separate panel and auto-link to the case via specimen barcodes. I recommend scanning specimen tubes immediately after collection rather than waiting until the autopsy is finished. The barcode matching in Idaho Autopsy Results resolves duplicates within about three seconds, but if you batch-scan fifty tubes at the end of a long day, you will occasionally get scan errors that require manual reconciliation and add forty-five minutes to your workflow. Report generation pulls from all completed sections into a template. You can choose from preloaded state-specific templates or import your own using the XML template editor. The export function produces PDF, Word, and CSV outputs. PDF signing requires a separate cryptographic certificate if you need NIST-compliant digital signatures for court-admissible documents. This is not included in the base license and runs about two hundred dollars per year for the certificate management module. Worth it if your office submits reports to courts regularly. Not worth it if you only generate internal summaries.
Get the Full Details
Common Problems and Workarounds
The most frequent issue I see with Idaho Autopsy Results is the timestamp desynchronization between the workstation clock and the LIS server. When the two clocks drift more than thirty seconds, case linkage fails silently. The system does not flag this error during normal operation. It surfaces later when you try to pull a cross-case timeline and find gaps. The fix is to enable NTP synchronization on every workstation and verify the drift is under ten seconds weekly. A quick command-line check using the system time settings takes about thirty seconds and prevents two hours of troubleshooting later. Another problem involves the backup routine. The built-in backup compresses the entire database into a single archive file, which works fine for small offices but becomes impractical past about five thousand active cases. The archive ballooned to nearly 18GB during a county-wide migration, and restoring it took eleven hours. I switched to incremental backups targeting the image cache separately from the core database, which reduced our restore windows to under ninety minutes. The trade-off is that you need to run two backup jobs instead of one, but the time savings during an actual disaster far outweigh the extra scheduling step. There is also a known limitation with the multi-user concurrent editing feature. If two pathologists attempt to modify the same case simultaneously, the second session receives a generic lock conflict message with no recovery option other than waiting for the first user to save and close the case. There is no queue or version-comparison tool. In practice, this means you need to establish a booking system for shared cases within your office. I set up a simple shared calendar that tracks which pathologist has exclusive edit rights at any given time, and conflicts dropped to near zero after we adopted that protocol.
Advanced Configuration for High-Volume Offices
Offices processing more than twenty autopsies per week should consider migrating off the embedded PostgreSQL database to a dedicated SQL Server instance. The embedded version handles moderate volume fine, but query latency increases sharply once you cross that threshold. Report generation times can jump from six seconds to over forty seconds during peak hours. SQL Server licensing is included in the Idaho Autopsy Results Enterprise tier, so upgrading the database backend costs nothing extra beyond the server setup time, which runs about two hours for an experienced administrator. The API endpoint for custom integrations is REST-based and uses JWT tokens for authentication. Documentation is available through the developer portal, but the examples lean heavily toward LIS integration scenarios. Custom dashboards or research data exports require you to write your own query builders. I built a Python script that pulls monthly cause-of-death statistics by zip code and writes them to a spreadsheet automatically. The script took about eight hours to develop because the API returns paginated results and requires careful handling of null fields in the manner-of-death columns. If your office needs regular automated reporting, plan for at least a day of development time per new dashboard. The system does not support mobile case review in any meaningful way. There is a basic web portal for viewing finalized reports, but you cannot enter new findings or approve drafts from a tablet or phone. This limitation matters if your staff works across multiple buildings or attends off-site coroner calls. The web portal was added in version 3.2, and while it loads cases in under three seconds on a good connection, the editing features are disabled. For remote sign-off, you still need to be at a workstation or request a printed copy for wet signature. Keep that in mind if your office is planning a hybrid workflow.
