Here are some sample functional requirements from the PACS RFP template:
|
| ►
Workstations
|
|
Provide graphical user interface (GUI) with toolbars and icons to initiate functions like printing, zoom, etc.
|
|
Provide ability to display ready-to-read images (leveled, zoomed, cropped, magnified, etc.) configurable on a per-user basis.
|
|
Provide ability to open and view multiple studies (e.g. current exams, old exams) in same session for comparison purposes.
|
|
Provide ability to attach manual annotations or "sticky note" comments to an exam that can be viewed on other workstations (e.g. ED "Wet Read").
|
|
Provide that multiple workstations do not require special software applications for Cobb Angle measurements.
|
| ►
Workflow
|
|
Support dynamically updated worklists (e.g. list of exams or patients) created by the system administrator for a specific user, class of users, or workstation.
|
|
Provide ability to assign worklists to a user, plus those assigned to the group of which the user is a member, plus those assigned to the workstation.
|
|
Automatically notify a member of the radiologist group when opening an unread exam which is already open by another member.
|
|
Automatically create a clinical folder for each patient and include three recent exams (e.g. current plus two prior).
|
|
Provide ability to select images or exams for inclusion into one or more manually-created folders for teaching and research purposes.
|
| ►
Storage
|
|
Provide ability to store un-processed image data in the buffer for a minimum of 14 days.
|
|
Images must not be stored with a non-reversible compression algorithm before the diagnosis of the exam is complete.
|
|
Provide ability for system administrator to protect selected images from deletion.
|
|
Provide ability to flag Pediatric and Mammography exams for infinite storage.
|
|
Automatically notify system administrator in the event of a system failure. (e.g. using SNMP Simple Network Management Protocol, or other method).
|
| ►
Archive
|
|
Provide sufficient on-line archival (e.g. long term) storage to provide access to at least five years of image production without intervention of a computer operator.
|
|
Automatically archive exams upon receipt into storage system, with option to queue exams for verification by use first.
|
|
The pre-fetching algorithm should have options that can be configured by system administrator to support internal policies and procedures.
|
|
Provide a reversible compression algorithm (e.g. DPCM with Huffman coding, or other) for use during archiving.
|
|
Allow the system administrator to designate the compression algorithm and configuration parameters individually for each modality.
|
| ►
Database
|
|
The PACS database should model all events, statuses and status changes necessary for proper synchronization with the RIS to support integrated, system-wide worklists.
|
|
Provide access control and security functions that enable assignment of unique privileges (e.g. displaying, de-archiving, QC of exams, etc.) to individual users and user groups.
|
|
Provide a DICOM Query/Retrieve SCP to support access by third-party components such as modalities and specialty workstations.
|
|
Provide ability for users to submit queries (e.g. SQL) to obtain lists of references (e.g. worklists and folders) representing a subset of the exams in the database.
|
|
Provide system-wide administration tools that facilitate security maintenance, worklist queries, system configuration, data integrity checks, etc. A graphical user interface is strongly preferred.
|
| ►
Image Acquisition
|
|
Provide image acquisition hardware and software to electronically communicate image data with DICOM and non-DICOM devices including modalities, review workstations, image printers, etc.
|
|
Provide one or more DICOM storage SCP (service class provider) which support all necessary storage SOP classes used in the DICOM image acquisition systems.
|
|
The image acquisition functions must accept, store and display the full, original image dataset transmitted from a digital modality to ensure maximum image quality and no degradation.
|
|
Provide functions for quality review of CR images for technologist to take remedial actions including image flip, image rotation, window width and level, image rejection or reprocessing.
|
|
The video acquisition component must allow the operator to acquire a single video image with a simple action (e.g. keystroke, mouse click, foot switch click).
|
| ►
Film Digitizers
|
|
Provide image acquisition hardware and software to electronically communicate image data with DICOM and non-DICOM devices including modalities, review workstations, image printers, etc.
|
|
Provide a DICOM Push Model SCP that transmits data to ancillary systems (e.g. treatment planning stations).
|
|
Any PACS interface to an imaging system must not cause a dependence on the operation of the PACS for its own operation. (e.g. must operate independently if network, interface, or unit fails).
|
|
Provide a video acquisition component to acquire video from non-digital modalities using the NTSC, PAL, SECAM, (or specify another) standard.
|
|
Provide ability to gather ultrasound images from a dedicated ultrasound local area network (LAN) via an external device DICOM interface.
|
| ►
Film Printers
|
|
Support laser film printers connected to the PACS network via camera server or spooler interface.
|
|
Support the DICOM Print Service Class as a Service Class Provider (SCP).
|
|
Print images as acquired or modified by a workstation, including image overlays and textual data.
|
|
Provide ability to select images and film format for printing remotely from the workstation or locally using keypad.
|
|
Provide printer self-diagnostics function that include check for film low, film empty, memory full, film null, film feed error, etc.
|
| ►
Web Access
|
|
Support World Wide Web (www) technology to allow Internet and intranet access to images using standard web browsers (e.g. Internet Explorer).
|
|
Provide sufficient configuration of web server hardware and software to provide access to PACS data and images over the internal network and handle anticipated request volume.
|
|
Provide ability for users to log on to PACS web server with secure passwords, request and view permitted images, and log off.
|
|
Support and display all worklists (via the web server) that are also accessible on the standard PACS workstations.
|
|
Support multi-level data and password security allowing system administrator to limit access to patient data on a per user basis by unit, floor, modality, physician group, etc.
|
| ►
Teleradiology
|
|
Support electronic transmission of radiological images from one location to another (including radiologists' homes) for interpretation and consultation.
|
|
Provide contractual commitment to support current and all future ACR/NEMA image data format standards and DICOM network standards.
|
|
Support transmission of small-matrix images (e.g. computed tomography (CT), magnetic resonance imaging (MRI), ultrasound, nuclear medicine, and digital fluorography).
|
|
Support annotation at the transmitting station including patient name, ID number, date/time of exam, institution of origin, type of exam, degree of compression (if any), and brief patient history.
|
|
Provide network and software security protocols to protect the confidentiality of the patient images and data.
|
| ►
Interfaces
|
|
Support data interface and integration with our RIS.
|
|
Support interface and gather data from this modality: .
|
|
| ►
HIPAA
|
|
Support an enterprise-wide single sign-on user authentication process that allows individual users to logon to different systems with one global user ID and password.
|
|
Support automatic log off of work stations connected to patient information systems after a site-defined time period of inactivity (e.g. 5 minutes).
|
|
Provide mechanism for entity (e.g. unique individual) authentication such as: biometric (e.g. hand geometry, retinal/iris scan, fingerprint patterns, facial characteristics).
|
|
Provide all necessary software upgrades to meet HIPAA compliance within 12 months after go live for new site implementations at no additional cost.
|
|
Provide ability to create redacted teaching files that meet HIPAA guidelines for compliance (e.g., tracking without specific patient information)
|
| ►
Technical & Support
|
|
Support graphical user interface GUI (e.g. Windows, buttons, toolbars, mouse, etc.) and menu-driven user control and initiation of system functions.
|
|
Support ability to use web browser (e.g. Netscape Communicator, Internet Explorer) to access system functions over Internet or internal intranet.
|
|
Support the use of "drag-and-drop" with mouse as option to visually initiate system functions (e.g. drag a file icon to printer icon to start printing a report, etc.)
|
|
Provide data management design that supports integration and sharing of data among all applications.
|
|
Provide sufficient back-up and recovery features to assure minimal data loss due to a system failure, power outage, etc.
|
| ►More... |
ACS)
and automatically
evaluate vendors' responses. 