|
Here are some sample functional
requirements for Clinical Data Repository: |
|
►
Provide data management system
features that allow for integration and sharing of data among all
applications. |
|
►
Provide data managment features
that eliminate the redundant maintenance of duplicate data. |
|
►
Support OLE (Object Linking and
Embedding). |
|
►
Support access to patient
records by alias name. |
|
►
Support access to patient
records by master person index identifier. |
|
►
Allow patients selected for
inquiry to be filtered by clinical department. |
|
►
Allow selection of procedures
for inquiry by procedure name. |
|
►
Provide ability to display
consolidated patient results from all medical facilities. |
|
►
Support display of all or
selected tests performed for the patient's current admission. |
|
►
Display available results and
indicated incomplete procedures as pending. |
|
►
Support automatic alerts when
life threatening or unusual results are identified (e.g. panic
results). |
|
►
Display data for results
inquiries including: alert flags for out-of-range results. |
|
►
Allow users to interactively
define which data elements can be graphed. |
|
►
Provide on-line, real-time data
transfer between CDR and <insert name> Hospital Information System. |
|
►
Provide on-line, real-time data
transfer between CDR and <insert name> Lab Information System. |
|
►
Provide patient-oriented (e.g.
versus encounter-oriented) organization of and access to patient
records. |
|
►
Indicate which facility
performed procedures in patient records. |
|
►
Support the collection and
storage of patient orders and status. |
|
►
Support the collection and
storage of transcribed radiology and pathology reports. |
|
►
Provide immediate access to and
keep patient records intact when patient is transferred from one level
of care to another. |
|
►
Support searching of patient
record (e.g. results and transcribed reports) using key words or
phrases. |
|
►
Allow consultation notes to be
appended to specific portions of a patient record via entry into
source system and transmission to data repository. |
|
►
Support inclusion (or link to)
one patients record to another's (e.g. mother's labor and delivery
record becomes part of newborn record). |
|
►
Provide ability to merge
duplicate patient records with proper user security. |
|
►
Support the concurrent display
of multiple types of data (e.g. radiology images, reports, lab results
and graphical displays). |
|
►
Support storage of and access
to multi-media including radiology images (e.g. support DICOM
standards). |
|
►
Support storage of scanned
documents from sources outside system such as transfer documents,
transport records, EKG strips from other facilities, etc. |
|
►
Provide translation
dictionaries or functions to assist in maintaining consistent data
coding across multiple medical facilities. |
|
►
Automatically print selected
types of reports based on pre-defined "time triggers." |
|
►
Allow medically related test
results to be grouped together on reports. |
|
►
Provide ability to generate ad
hoc queries and reports of ANY stored data without programming. |
|
►
Allow data extracted by one
query to be accessed and manipulated with other queries. |
|
►
Support output of queries and
reports to HTML format for intranet or intranet web (e.g. WWW, World
Wide Web) publishing. |
|
►
Provide standard surveillance
reports (e.g. infection control, CQI, QA, risk management, workload
management). |
|
►
Provide security checks to
control user access to patient information based on: user ID. |
|
►
Support controlled external
access from remote sites (e.g. using call-back security system with no
direct modem lines into system). |
|
►
Maintain security audit trail
of all unsuccessful system logons including user ID, date and time. |
|
►
Provide ability to prohibit
unauthorized downloading of data to intelligent workstations and PC's. |
|
►
Provide complete turnkey
on-site implementation and project management support. |
|
►
Support ability to use web
browser (e.g. Netscape Communicator, Internet Explorer) to access
system functions over Internet or internal intranet. |
|
►
Provide multi-level password
security down to options within menus. |
|
►
Maintain and allow on-line
access to a system-wide data dictionary. |
|
►
Provide data management design
that supports integration and sharing of data among all applications. |
|
►
Support ODBC (Open Database
Connectivity) protocols for data access. |
|
►
Support TCP/IP networking
protocols for communication among networked devices (e.g. PC's, file
servers, networked printers). |
|
►
Provide interface to and allow
archival of data on optical disc storage media. |
|
►
Provide technical documentation
for support staff including system overviews, design, flowcharts, and
file layouts. |
|
►
Supply all computer program
source code on media (e.g. tape, CD) to user. |
|
►
Provide future software
releases and updates to all applications as part of regular software
maintenance fees. |
|
► More... |
.