1 / 9

HAIMS Site Assistance Requirements

HAIMS Site Assistance Requirements. 11 April 2013. Overall Site Support Requirements. AutoRelay Servers CHCS Interface PACS Interface HAIMS Account Management. HAIMS High-Level Diagram. 1. AutoRelay Server. Purpose

ayita
Télécharger la présentation

HAIMS Site Assistance Requirements

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. HAIMS Site Assistance Requirements 11 April 2013

  2. Overall Site Support Requirements • AutoRelay Servers • CHCS Interface • PACS Interface • HAIMS Account Management

  3. HAIMS High-Level Diagram

  4. 1. AutoRelay Server • Purpose • Provides interface to all site Multi-functional Devices (MFDs) and network scanners. Aggregates all traffic and sends it to HAIMS from one IP address for easier management of site PPS and firewalls • Setup / Integration (One Time Effort) • Site to select a device to serve as the AutoRelay Server • Set up and configure AutoRelay Server to connect to HAIMS and test • Configure AutoRelay Server for MFDs and network scanners • Sustainment • Modify configuration to add or remove MFDs and / or network scanners • Provide DCO or WebEx access to AutoRelay Server to HAIMS Sustainment team for troubleshooting

  5. 2. CHCS Interface • Purpose • Provides HAIMS with the HL7 completed study report. HAIMS uses this message as trigger to register DICOM images in the Regional PACS archives • Setup / Integration (One Time Effort) • Site to configure CHCS HL7 transmitter to send a copy Completed Study report to the specific HERA that interfaces with Regional PACS where the study resides • Sustainment • Support any troubleshooting efforts if there is an issue with the CHCS – HAIMS interface • Touch labor support for shared chassis

  6. 3. PACS Interface • Purpose • Interfaces provides the ability to perform DICOM queries to register studies into HAIMS to provide global awareness and access. When a user request the study, HAIMS will retrieve the DICOM image and make it available to the user • Setup / Integration (One Time Effort) • Update configuration to provide HAIMS access the Regional PACS archive • Sustainment • Support any troubleshooting efforts if there is an issue with the PACS – HAIMS interface

  7. 4. HAIMS Account Management • Purpose • HAIMS has it own AD that it uses to authenticate users for both stand-alone and AHLTA-embedded mode. This includes adding HAIMS roles to non-AHLTA users and deleting accounts to users that no longer require access • Setup / Integration (One Time Effort) • Add all non-AHLTA users that require access to HAIMS with the proper HAIMS role • Sustainment • Provide account management including adding or modifying HAIMS roles and deleting accounts for users no longer needing access

  8. Requirements Assignment Support Matrix (Suggested)

  9. “HAIMS—Global Awareness and Access of Artifacts and Images” 9

More Related