R1-2013
Request for Information
Health Terminology Server
For the Israel Ministry of Health
Document Version:
Date:
1.0
March 19, 2013
Table of Contents
1
INTRODUCTION............................................................................................................................... 3
1.1
1.2
1.3
1.4
1.5
1.6
1.7
2
PURPOSE OF THE RFI ........................................................................................................................ 6
2.1
3
ISRAEL HEALTH TERMINOLOGY PROJECT............................................................................................. 3
3
BACKGROUND ............................................................................................................................... 3
SOLUTION PURPOSE ....................................................................................................................... 4
STATEMENT OF NEED...................................................................................................................... 4
SOLUTION SCOPE ........................................................................................................................... 4
TERMINOLOGY .............................................................................................................................. 5
LANGUAGE ................................................................................................................................... 6
ADMINISTRATIVE REQUIREMENTS .................................................................................................. 6
3.1
LEGAL PROVISIONS......................................................................................................................... 6
3.1.1
Non-Committal ................................................................................................................ 6
3.1.2
Confidentiality .................................................................................................................. 6
3.1.3
Liability for Errors ............................................................................................................. 6
3.1.4
Modification of Terms ...................................................................................................... 7
3.1.5
Ownership of Proposal ..................................................................................................... 7
3.2
RFI RESPONSE INSTRUCTIONS ......................................................................................................... 7
3.2.1
Response Submittal ......................................................................................................... 8
3.2.2
Contacts ........................................................................................................................... 8
3.2.3
Qualifications ................................................................................................................... 8
4
REQUIREMENTS FOR THE ISRAEL HEALTH TERMINOLOGY STANDARDIZATION (IHTS) PROJECT .. 8
4.1
GENERAL SOLUTION REQUIREMENTS ................................................................................................. 8
4.2
TECHNICAL REQUIREMENTS - EVALUATION CRITERIA .......................................................................... 11
4.2.1
Part 1 – Company Information ..................................................................................... 11
4.2.2
Part 2 – Hardware and Software Requirements .......................................................... 12
4.2.3
Part 3 – General Requirements .................................................................................... 14
4.2.4
Part 4 –Terminology Management ,Definitions and Interfaces ................................... 15
4.2.5
Part 5 –Administration ................................................................................................. 18
4.2.6
Part 6 – Front-End ........................................................................................................ 20
4.2.7
Part 7 – Project/Solution Level System Administration................................................ 21
4.2.8
Part 8 – Front-End Infrastructure for Accessibility ....................................................... 21
4.2.9
Part 9 – Cost Structure .................................................................................................. 23
4.2.1
Part 10 – Past Projects and References......................................................................... 23
4.2.11
Part 11 – Implementation and Support ........................................................................ 24
4.2.12
Part 12 – Consultation .................................................................................................. 25
4.3
APPENDICES ............................................................................................................................ 26
4.3.1
Appendix 1 – Partially Supported or Non-Supported Requirements .............................. 26
4.3.2
Additional Comments .................................................................................................... 28
Israel Health Terminology Project - RFI
Page | 2
1 Introduction
1.1 Israel Health Terminology Project
The Israel Health Terminology Server (IHTS) Project is initiated by the Israel Ministry
of Health (IMH).
1.2 The objective of the IHTS project is to standardize the data which
flows among the various entities in the Israel Health System.
1.3 IHTS Project Management
The IHTS project is being managed by the Information and Computing Division of the
IMH.
1.4 Information and Computing (IT) Division of the Israel Ministry
of Health
The IT Division of the IMH leads the regulatory activity of the medical information
systems within the Israel health system, and promotes the use of information
systems in order to improve the medical treatment and services provided to the
health service consumers.
Its roles and responsibilities include leading the management of medical information
within the Ministry and its utilization in an effort to improve decision making
processes within the Israel health system; responsibility for Ministry regulation of
the medical information systems; leading processes intended to improve the use of
medical information systems within the Israeli health system; responsibility for
regulation of information security within medical institutions; and promoting the
issue of medical information management in Israel .
1.5 Background
The IMH is leading a number of initiatives which share the same goal; improve the
capabilities of the health system in Israel for data sharing.
To achieve that, IMH has decided to carry out the following initiatives:
 Implementation of SNOMED-CT as the core clinical terminology in the Israel
health system.
 Upgrade from ICD-9-CM to ICD-10-CM for reporting and billing purposes.
 Standardize the health services codes in Israel, both in hospitals and in the
community.
 Development of a National Pharmaceutical Catalog (NPC).
Israel Health Terminology Project - RFI
Page | 3

Create a master set of laboratory test codes based on LOINC and map all
other local codes accordingly
IMH will be responsible to manage the terminology at the national level. Updates
will be made periodically and be distributed to all health care entities through the
standard channel
1.6
Solution Purpose
The IHTS project is seeking a software solution from qualified vendors to provide a
Terminology Server (TS) to serve as a platform for the management of Health
terminologies and catalogs in Israel.
1.7
Statement of Need
The software solution will be a centralized Terminology Server (TS) for the
management of Health terminologies and catalogues throughout the State of Israel.
A unit belonging to the Israel Ministry of Health will maintain and operate the
system and its data on a day-to-day basis.
The data contained in the TS will be made available to the general public through a
front-end Internet Gateway or Portal. While the front-end is not necessarily within
the scope of this RFI, the TS System is expected to support the discovery and access
of the records and their related digital surrogates, including images and audiovisual
material.
1.8 Solution Scope
The complete solution will consist of the following elements:
1. International terminologies include at least:
a. SNOMED-CT
b. ICD-9-CM
c. ICD-10
d. ICD-10-CM
e. LOINC
f. RxNORM
g. ATC
2. Local terminologies:
a. Procedures based on expanded ICD-9-CM
b. National Pharmaceutical Catalog
c. National Health Services Catalog
Israel Health Terminology Project - RFI
Page | 4
1.9 Terminology
"ICD"
The International Classification of Diseases (ICD) is the
standard reporting tool for epidemiology, health
management and clinical purposes. This includes the
analysis of the general health situation of population
groups. It is used to monitor the incidence and
prevalence of diseases and other health problems.
It is used to classify diseases and other health problems recorded on many types of
health and vital records including death certificates and
health records.
"Requesting Parties"
The IHTS Project management as defined herein.
"Respondent"
Any qualified party to provide the Solution, who
submits a response to this RFI.
Request for Information (RFI) is a
standard business process whose purpose is to collect
written information about the capabilities of various
suppliers.
"RFI"
"RFP"
A request for proposal (RFP) is issued during
a procurement process, where an invitation is
presented for suppliers, often through
a bidding process, to submit a proposal on a
specific commodity or service.
"Selection Procedure":
The entire procedure conducted by the requesting
parties to collect information about the available
solutions as set out in this RFI.
"SNOMED-CT"
"Surrogate"
Systematized Nomenclature Of Medicine Clinical
Terms (SNOMED-CT), SNOMED CT is a clinical
healthcare terminology that provides the core general
terminology for the electronic health record (EHR) and
contains more than 311,000 active concepts with
unique meanings and formal logic-based definitions
organized into hierarchies
Copy or replacement of the original.
"TS"
Terminology Server
Israel Health Terminology Project - RFI
Page | 5
2 Purpose of the RFI
The IHTS Project is publishing this RFI for the purpose of gathering information on
the capabilities of available solutions. This RFI will in no way limit or otherwise bind
the IHTS Project to the vendors who have replied to the RFI and do not constitute
any undertaking by any of the project participants referred to herein.
2.1 Language
This RFI was written and will be published in English so that a maximum number of
solution providers from Israel and around the world can read and respond to the RFI.
Responses to this RFI may be submitted in English or Hebrew.
3 Administrative Requirements
3.1 Legal Provisions
By agreeing to receive and/or by responding to this RFI, each Respondent accepts
and undertakes to comply with the following terms and conditions:
3.1.1 Non-Committal
Nothing in this RFI, nor any communication made by the IHTS Project, Israel Ministry
of Health, or the agents, employees or advisers thereof shall constitute an offer of a
contract or a binding contract between the requesting parties and any prospective
Respondent, nor shall it be taken as constituting any representation that rights or
licenses will be granted in accordance with this RFI.
The RFI may form the basis for a future and separate RFP tendering process between
the IHTS Project and the Respondent for the supply and implementation of the TS
System as set out in the RFI document.
3.1.2 Confidentiality
All information received in this RFI will be kept confidential and only for the
knowledge of the requesting parties and purposes of this RFI. The Israel Ministry of
Health may share the information gathered with other governmental agencies or
state-owned companies, including hospitals and HMOs. The information can also be
shared with vendors or consultants assisting the Israel Ministry of Health with the
IHTS project.
3.1.3 Liability for Errors
While the IHTS Project has made considerable effort to ensure an accurate
representation of information in this Request for Information, the information
Israel Health Terminology Project - RFI
Page | 6
contained in this Request for Information is supplied solely as a guideline for
Proponents. The information is not guaranteed or warranted to be accurate by the
requesting parties, nor is it necessarily comprehensive or exhaustive.
3.1.4 Modification of Terms
The requesting parties reserve the right to modify the terms of this Request for
Information any time at its sole discretion. This includes the right to cancel this
Request for Information at any time. Updates to the RFI will be published on the
Israel Health Ministry website.
3.1.5 Ownership of Proposal
All documents, including responses and proposals, submitted to the requesting
parties become the property of the requesting parties. They will be received and
held in confidence by the requesting parties.
3.2 RFI Response Instructions
To answer this RFI please fill in the attached form (Section 4.2, "Evaluation Criteria").
The contact person listed below is available for assistance if necessary.
An evaluation committee comprising representatives from the Israel Ministry of
Health will evaluate the answers to this RFI.
For each requirement, you are requested to fill out the Response and Explanation
columns. Each requirement is followed by a detailed explanation in smaller print.
Response Column:
Answer "Fully Supported" if your solution FULLY meets the requirement "out of the
box" with no further development and/or customization necessary.
Answer "Partially Supported" if your solution PARTIALLY meets the requirement
and/or some further development and/or customization may be necessary to meet
the requirement. Please state how many man days of work are required in order to
fully complete this feature. (See Appendix 1 below).
Answer "Not Supported" if your solution DOES NOT currently meets the
requirement and/or it must be fully developed. Please state how many man days of
work are required in order to fully complete this feature if you intend or are
otherwise considering adding this feature. (See Appendix 1 below).
Answer "3rd Party Supported" if your solution DOES NOT currently meet the
requirement however a 3rd party has successfully developed and implemented a
solution for the requirement and it works successfully with your solution.
Israel Health Terminology Project - RFI
Page | 7
NOTE: The responses must reflect the current status and features of your product. If
your solution does not currently meet the requirement but will do so in the future,
please describe the future planned development in the response field.
Details Column: For each requirement, please provide a FULL and DETAILED
explanation on how your solution meets or exceeds the requirement. You may
include charts and illustrations where necessary.
A requirement left blank will be evaluated as "NOT SUPPORTED".
At the end of each section there are two blank fields "Additional Features" and
"Additional Comments". Any additional features or comments that the solution
provider may wish to describe should be entered here.
3.2.1 Response Submittal
Send the attached form in word-format (format unchanged) by email to
Michrazim_Michshuv@MOH.HEALTH.GOV.IL by April 28, 2013.
3.2.2 Contacts
For questions regarding this RFI, you are welcome to contact:
e-Mail: Michrazim_Michshuv@MOH.HEALTH.GOV.IL
3.2.3 Qualifications
This RFI has been designed to gather information from companies with: (a) extensive
proven experience in providing the software solution and working with health
organizations; (b) extensive knowledge and understanding of health terminology
standards and practices; (c) a strong financial background; (d) sufficient financial and
human resources to provide the solution; (e) solid experience and a state-of-the-art
information technology infrastructure.
4 Requirements for the Israel Health Terminology
Standardization (IHTS) Project
4.1 General Solution Requirements
The requirements listed in this section outline the basic requirements that the
solution will be expected to meet. A more detailed list of the individual
requirements appears in Section 4.2 of this RFI.


The System will support all elements specified in paragraph 1.6 above.
Actions on each terminology managed on the server:
o Input of new versions on a regular basis, predetermined by the
Israel Ministry of Health.
Israel Health Terminology Project - RFI
Page | 8

o
o
o
o
o
o
o
The system will support comparison between the different
versions including highlighting the differences between the
versions (current version and new one).
 The system will display the new content in the new
version, compared to the local expansions that have been
made to the terminology.
Mapping all of the different terminologies displaying where there
is an international mapping of this type, and capabilities to
develop local mappings. Mapping of international codes should be
available as part of the solution. In addition, local mapping
capabilities should be available as well.
Mapping of current version (international and local) should be
kept during upgrade to a new version. The “delta” between the
two versions must be available for distribution to all health care
entities
Local update of the terminologies - addition of new concepts and
relationships:
 Single additions.
 Batch additions based on file importing.
 Performance of quality assurance on every new concept
entered into the system. (does it exist, is it complete, is the
structure appropriate, is its position (node) on the data
tree appropriate.
Mapping update between the various terminologies.
Ability to map legacy terminologies extant today in the various
health institutions on to international terminologies
Creation, update and distribution of RefSets (Selected collection of
concepts) for each of the terminologies (international and local).
 Existence of automatic mechanisms as much as possible, to
create the RefSets including utilization of the attributes of
the terminology (hierarchy and other relationships).
Terminology Display
 Display of every concept including all of its characteristics:
Code (concept and term), parents, children, other
relationships, definition (if exists) - ability to navigate to
any other concept/term displayed.
 Graphic display of a tree, including all relationships of the
selected concept.
 Display a result of a search in list form.
 The display will be done in a user-friendly fashion (use of
icons or similar in order to ease use by lay users).
Israel Health Terminology Project - RFI
Page | 9
o Fast and high-standard searches in terminologies using:
 Search by name (chosen name, synonym).
 Search by code.
 Fast search, complementary.
 Tree navigation (up and down).
 Semantic inquiry ability as a basis for inquiry of databases
that contain terminology codes (mainly for SNOMED), i.e if
we want to build a query to extract from the database all
cases of stroke, we need to be able to extract all the codes
that have to do with these cases. Inquiries of these type
can be complex as they depend on the relationships and
definitions in the terminology.
o The system will enable terminology update, RefSet building etc. by
a number of users at the same time.
o Export of terminologies - full or partial(RefSets) to:





Excel Tables.
Local updated version of SNOMED in SNOMED format
(RF2).
 Text Files.
 XML Files.
o Distribution - Ability to distribute each terminology or parts of to
many addressees at the same time in one of the above formats.
Automatic processes should be put in place. Also the mechanism
should include error handling especially in case of distribution
failure…
Ability to enable searching terminologies using Internet browsers by tens
of thousands of users concurrently. – Performance. Response time of no
more than 2 sec.
Ability to use the API of the application to develop local functionality:
o Fast search of Clinical health records to find specific terms.
o Coding hospital diagnoses.
General requirements:
o Access permit according to number of valid licenses including
management of expired licenses.
o Documentation of user problems in use of the system such as
import and export of files.
o Usage documentation.
o Multi-user support with no deterioration in performance.
o High uptime.
Israel Health Terminology Project - RFI
Page | 10
o Simplicity - interface that enables users to achieve use of the
system without need for professional training.
o Fast responsiveness of system.
o Fast and high standard searches.
o Support of standards such as HL7.
o The System will support backup and restore functionality of the
system and its data via a built-in or third party application.
o Need to define a clear SLA and include helpdesk, maintenance and
support. Include roles, responsibilities and response time
o Reporting – The system will provide reports:
 On the individual terminology level for use by each
terminology.
 On the system administrator level providing data regarding
the number of terminologies in the system, the number of
objects, users, use of the system by each terminology.
4.2 Technical Requirements - Evaluation Criteria
4.2.1 Part 1 – Company Information
Item
Company name
Company location
Company website
Details
Main products/services
Click here to enter text.
Main market/customers
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text
Ownership structure with ownership status Click here to enter text.
in percentage
Click here to enter text.
Structure of mother corporation, joint
ventures, subsidiaries, partnerships or other
relevant relations
Click here to enter text.
Number of years on the market
Experience in other similar projects
Click here to enter text.
Experience with governmental health
institutions
Ability to manage project in such scale –
please specify project managers
Company location(s)
Click here to enter text.
Israel Health Terminology Project - RFI
Click here to enter text.
Click here to enter text.
Page | 11
Describe your business continuity
management
Enable a local representative to provide
help during implementation – please
specify local partners in Israel
Contact person and responsible for
answering this RFI
Position of contact person
Click here to enter text.
Telephone (land line and cellphone)
Click here to enter text.
Email
Click here to enter text.
Click here to enter text
Click here to enter text.
Click here to enter text.
4.2.2 Part 2 – Hardware and Software Requirements
Item
Name of Solution/Product that pertains to the
RFI
Product/Solution Description
Response
Number of customers using the solution
Click here to enter text.
Solution developed by
Click here to enter text.
License Type Licensing agreements (can a single
license be used for multiple users?), Site
licensing is available?, Options for licensing
incentives? - Please specify
Purchasing cost model (one-time cost? On-going
licensing costs? Base cost, Is the product open
source or proprietary? - Please specify
System Requirements (OS, Software, Hardware,
VM, 64-bit OS support)
What technologies does the solution use?
Click here to enter text.
Database (default/ supported)
Click here to enter text.
Technical Architecture
Click here to enter text.
Solution Hosting (default / supported) –
specifically, can the product be hosted locally in
the IMH's datacenter?
Click here to enter text.
Israel Health Terminology Project - RFI
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Page | 12
Demo/Sandbox Available?
Click here to enter text.
Is the software is designed specifically for
Terminologies?
Please include a list of current customer
references
Click here to enter text.
Click here to enter text.
(including contact information)
In what encoding is input text stored
Click here to enter text.
Is the software multilingual
Click here to enter text.
(including support for right-to-left languages i.e. Hebrew,
Arabic)
Is the software available in Israel
Click here to enter text.
Frequency of major version releases
Click here to enter text.
Frequency of minor releases (bug fixes)
Click here to enter text.
Are bug fixes and feature developments
included for all customers in each version of the
software?
Batch/bulk terminology loader available?
Describe.
Export function to extract information out,
instead of one screen at a time on the monitor?
Describe.
Ad hoc and format-specific exporting (RRF, OWL,
Proprietary (HL7), etc.).
How third-party applications integrate with the
system.
How the system supports 24/7 availability, failover features, volume, and scalability.
Database engines supported by the system.
Click here to enter text.
Customization flexibility – how customizable is
the solution. (Please describe)
Solution Scalability
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
How scalable is the solution? (in terms of hardware,
software, how many records and institutions can be
added)
Source code escrow
Click here to enter text.
(Is your company willing to commit the software source
code to an escrow)
Customer Support and Training
Support in Hebrew is available in Israel
Click here to enter text.
Customer support forum
Click here to enter text.
Israel Health Terminology Project - RFI
Page | 13
Online Help manual in Hebrew, English
Click here to enter text.
SLA – Please describe your levels of SLA
Click here to enter text.
Technical Documentation
Click here to enter text.
Customer support methods and availability
Click here to enter text.
(phone hotline, web chat, email, remote support access,
etc…)
4.2.3 Part 3 – General Requirements
Requirement
Support the ability to create and maintain an
accessible preservation or "backup" data source
of the data of all the terminologies in the System.
Response
Details
Choose an item.
Click here to enter text.
Allow each individual terminology to fully manage
its collections and records as detailed in the RFI
requirements below remotely.
Allow terminologies that already have an TS to
export their records to the IHTS System. The
System will import this data seamlessly in an
automatic or semi-automatic fashion.
Support mechanisms for restricting selected
records and digital images from public access
according to accepted standards.
Does the system include a Front-End Web
interface for use by the public for accessing the
content? If not, how does the system integrate
with a front-end system?
Built-in backup and restore capability
Choose an item.
Click here to enter text.
Choose an item.
Click here to enter text.
Choose an item.
Click here to enter text.
Choose an item.
Click here to enter text.
Choose an item.
Click here to enter text.
Performance:
Support of at least 50 concurrent users
Response time 2 seconds or less
Choose an item.
Click here to enter text.
This data source must be accessible directly without the
need for proprietary software.
Israel Health Terminology Project - RFI
Page | 14
4.2.4 Part 4 –Terminology Management ,Definitions and Interfaces
Item
Terminology Management
International Terminology
Response
Local Terminology
Click here to enter text.
Support of specific terminologies - ICD9, ICD10,
SNOMED-CT, LOINC, RxNorm etc.
Mapping between Terminologies
Click here to enter text.
Ability to update terminology and relationships
locally (based on user access rights)
Map local versions of the terminology to the
standard one (e.g. CPLP to LOINC)
RefSet Creation - batch
Click here to enter text.
Terminology view (UI) – textual and graphic
(using product tree)
Update terminology in refset of several users
Click here to enter text.
Services within the system to address specific
meta-management of multiple terminologies
(e.g., how will DI processes for relevant priors be
captured?).
Describe how the system advises subscribers on
new code/updated code sets availability.
Describe the system’s ability to support bidirectional mappings
Match & Merge abilities - batch
Click here to enter text.
Ability to manage parallel catalogs for different
purposes
Pharmaceutical Catalog management option
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Code sets tracked with statuses—pending,
review, approved, superseded, obsolete?
Ability to map one-to-one and one source code
to multiple target codes? Must also have the
ability to provide a description of the source of
the translation, when created, how done etc.
Israel Health Terminology Project - RFI
Page | 15
Ability to signify the quality of the translation
(e.g., exact, narrower, broader, partial, etc.).
Does the system support concept-based,
standard, structured, formal terminologies?
Does the system manage extension concepts
consistent with the terminology model of the
base terminology being extended? At a
minimum the extension concepts must be
"placed" in the correct hierarchy (or hierarchies)
and with more complex terminology models
(such as SNOMED CT) additional concept
relationships are also included.
Does the system support the maintenance of
local extensions that utilize external
Terminology Authorities such that an
introduction of a new version does not require
re-creation of the existing extensions?
Describe how the system supports the creation
and maintenance of subsets (e.g., Diagnostic
Imaging (DI) procedures from SNOMED-CT to
support Diagnostic Imaging solutions).
Describe how the system imports and maintains
SDO cross-mapping material.
Describe how the system is capable of
maintaining large-scale terminologies (e.g.,
SNOMED-CT, LOINC) as well as small-scale
vocabularies and codes.
Describe how the system is able to address the
following: Mapping between concepts in a
reference terminology and legacy terms/codes
or between concepts in different source
terminologies or application vocabularies. The
software should be capable of creating maps
through representation synonymy, term
association, relationship, attribute, layers of
granularity, composition/decomposition, etc.
The cross-reference map should account for all
concepts and terms.
Describe how the system supports the
designation of terminology and/or terminology
sets as specific to a particular realm.
Israel Health Terminology Project - RFI
Page | 16
Describe how the system handles parent-child
and sibling relationships.
Describe the features that the product supports
for concept extracting from free text.
Describe the features available for import and
export (e.g., full terminology sets, subsets,
mapping. What formats? What impacts to the
system? Etc.).
Describe the system’s ability to maintain
reference terminology extensions.
Describe how the system responds to a specific
domain requirement, particularly when a new
concept is required to meet provincial needs and
won't be available in the reference terminology
until the next update.
Describe how the system preserves the integrity
of mapped data when there are updates of new,
deleted, and changed terms. The software
should be capable of producing timely versions
of mappings.
Describe how license information (date,
duration, cost, supported languages, supported
relations, supported properties, etc.) is stored
for each vocabulary domain.
Interfaces
Click here to enter text.
Support standards: HL7 and other
Export reports of terminology in different
formats
Distribution - Push and pull terminology to
health care providers
Ability to interface with local applications /
databases
Easily interfaced to other standard operational
and ERP systems – please specify any existing
interfaces that can be included as part of the
basic offering
Is it possible to use as an organizational EDM –
for managing local dictionaries such as
countries, cities etc
Israel Health Terminology Project - RFI
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Page | 17
4.2.5 Part 5 –Administration
Administrative Functions
Administration Interface
Choose an item.
Click here to enter text.
User Permissions – for users - both for single users Choose an item.
and user groups
Click here to enter text.
(such as internal users, archivists, external users)
Control access permissions to records
with user profiles including : Data attribute (field)
level security, Access control of data (read, write,
delete, copy), etc.
Record and maintain usage data of archival users
Choose an item.
Click here to enter text.
Choose an item.
Click here to enter text.
Record and maintain usage data of terminology
material access history.
Ability to link between terminology users and
terminology material access history
Ability to define (on/off) fields as searchable by
the search engine
Synchronization with other cataloging systems
Choose an item.
Click here to enter text.
Choose an item.
Click here to enter text.
Choose an item.
Click here to enter text.
Choose an item.
Click here to enter text.
Choose an item.
Customization/ Configuration of the user
interfaces, fields, functionality
Choose an item.
Audit trail of data changes- including:
 Versioning – Maintaining historical data
and changes log
 Ability to track a term / concept to its form
at a certain date in history
 Can data be configured with an expiry date
 How archived data is accessed
 Comparison on deltas between full-set
versions, (new, deprecated, the same)
 Comparison on deltas of two subsets
created from the same terminology (e.g.,
DI Procedure subset v1.0 to DI Procedure
subset v2.0 from SNOMED-CT) and
produce a delta report.
 Describe how the system is able to merge
subsets (e.g., DI Procedure subset v1.0 to
DI Procedure subset v2.0) created from
the same terminology to obtain a new DI
Procedure subset v3.0 consisting of entries
Click here to enter text.
Israel Health Terminology Project - RFI
Click here to enter text.
Page | 18
from both subsets
Bug Reporting, including also documenting all
issues with data entry or batch processes,
especially uploading or downloading, or other
failures
Version absorption
Choose an item.
Click here to enter text.
Choose an item.
Click here to enter text.
Support export/import of data extracts
Choose an item.
Click here to enter text.
Support timely updating of information; critical
updates take place immediately
Choose an item.
Click here to enter text.
Support multiple users
Choose an item.
Click here to enter text.
Accessible from remote locations
Choose an item.
Click here to enter text.
Describe the security model
Choose an item.
Click here to enter text.
Indicate whether the product works with twofactor authentication
Does the system support role-based access?
Choose an item.
Click here to enter text.
Choose an item.
Click here to enter text.
Choose an item.
Click here to enter text.
Choose an item.
Click here to enter text.
Choose an item.
Produce list of all or partial terminology holdings
based on numerous selectable criteria, with ability
to select the fields to be displayed in the report.
Click here to enter text.
Reports
Reports and usage statistics
Print/save/email
Reports:
List all built-in reports available
(Please note any limitations such as number of fields or
reported items)
Indicate whether reporting tools are supplied with the product
out of the box.
Describe the tools available for reporting
Describe custom reporting that is available
Indicate whether the product supports ad hoc queries using
Boolean logic.
Indicate whether the product supports SQL queries
Israel Health Terminology Project - RFI
Page | 19
4.2.6 Part 6 – Front-End
User Access
Authorization levels for system access
Choose an item.
Click here to enter text.
Choose an item.
Click here to enter text.
Choose an item.
Click here to enter text.
Choose an item.
Click here to enter text.
Choose an item.
Click here to enter text.
Customizable UI
Choose an item.
Click here to enter text.
Multi-Language – Individual user can select
desired interface language (Hebrew, English,
Choose an item.
Click here to enter text.
Choose an item.
Click here to enter text.
Save Reports
Choose an item.
Click here to enter text.
Email reports
Choose an item.
Click here to enter text.
Print Records
Choose an item.
Click here to enter text.
Other
Additional comments
Click here to enter text.
Remote Data Entry
Allows for external users to connect to
backend system and insert/retrieve records
information
Data Entry Approval Process
Allow for proofing /approval /publish/reject of
new records from external users
User Interface
User interface is: Web Interface / Client /
Application.
(Please describe the UI technology)
Please provide screen shots for the 10 main screens at
least
Demonstrate the following issues:
 Consistent user interface: screen layouts,
keyboard functions, navigation
 Simple and intuitive GUI
 Provision by menus access to all applications
 Quick paths provided from one function to
another
 Easily understood
 Easy to learn how to use its functions
Built-in Help
(user manual, online help, field and functionality help
lookup)
Arabic, French, German, Russian). The interface switches
to right-to-left for right-to-left languages.
Reports
Reports
Usage reports, usage statistics – of the user
Israel Health Terminology Project - RFI
Page | 20
4.2.7 Part 7 – Project/Solution Level System Administration
System Administration
Module for the management of many
terminologies in a hosted environment
Choose an item.
Click here to enter text.
Management mechanism for different types of
authorization levels regarding national or local
(organizational) terminology (within
organizations, national level, etc.)
Approval workflow for adding concepts
Choose an item.
Click here to enter text.
Choose an item.
Click here to enter text.
Define system-wide workflows
Choose an item.
Click here to enter text.
Choose an item.
Click here to enter text.
System checks for data corruption and
damaged or missing files
Disaster recovery: what can and cannot be
restored, Are there out-of-the-box backup and
recovery plans?
Other
Additional features
Choose an item.
Click here to enter text.
Additional comments
Click here to enter text.
by the technical management team of the project
A single workflow for many terminologies
Ability to customize workflows – without
requiring additional development or vendor
support.
Required on a per-terminology basis. However
different workflows can be defined for different
terminologies in the system, and a workflow can be
defined and then used for a number of different
terminologies in the system.
Click here to enter text.
4.2.8 Part 8 – Front-End Infrastructure for Accessibility
Does your system have a Front-end Web interface
for presentation of the terminology material to
the public?
How does your solution integrate with a 3rd party
developed front-end?
Do you supply an API?
Choose an item.
Click here to enter text.
Choose an item.
Click here to enter text.
Choose an item.
Click here to enter text.
Do you supply an SDK?
Choose an item.
Click here to enter text.
Supported Browsers and versions
Choose an item.
Click here to enter text.
Israel Health Terminology Project - RFI
Page | 21
Multimedia support
Choose an item.
Click here to enter text.
Integration with social media platforms
Choose an item.
Click here to enter text.
Support and manage interaction with public users
including feedback, orders, questions, requests.
Ability to create, edit, e-mail, share, and save a
search list of items.
Prevent unauthorized copying/downloading of
digital material
User interface:
Choose an item.
Click here to enter text.
Choose an item.
Click here to enter text.
Choose an item.
Click here to enter text.
Choose an item.
Click here to enter text.
Choose an item.
Click here to enter text.
Choose an item.
Click here to enter text.
Search on date ranges (from year to year)
Choose an item.
Click here to enter text.
Browse feature
Choose an item.
Click here to enter text.
Search on fields and/or keywords –globally on all
fields and levels of hierarchy
Refine search based on hierarchy, type of item,
collection, terminology
Create search query from keywords and phrases
from keywords table
Search results clearly indicate hierarchical
relationships of records
Search result clearly indicates location of record
within hierarchy
Ability to move up or down in the hierarchy
without having to perform new search
Federated Search
Choose an item.
Click here to enter text.
Choose an item.
Click here to enter text.
Choose an item.
Click here to enter text.
Choose an item.
Click here to enter text.
Choose an item.
Click here to enter text.
Choose an item.
Click here to enter text.
Choose an item.
Click here to enter text.
Support search on OCR of digital images
Choose an item.
Click here to enter text.
Keywords / stop-words lists
Choose an item.
Click here to enter text.
Multi language thesaurus / keywords tables
Choose an item.
Click here to enter text.
Describe to what degree keyboard shortcuts are defined
(copy/paste, repeat last action, undo, help, spell check).
Indicate whether the product uses drag-and-drop
functionality.
Describe how a user navigates through the product
Search / Information Retrieval
Search Engine - Does the solution include a search
engine?
Which search engine does the system use? (in-house or 3rd
party?)
Search types /interface
Basic/advanced search – describe the search options and
depth of search
Choos
Quick search for relevant data across entities
Israel Health Terminology Project - RFI
Page | 22
Semantic search using drug name or indication
Choose an item.
Click here to enter text.
Advanced search for smart users
Choose an item.
Click here to enter text.
Use search API in other applications like EMR
Choose an item.
Click here to enter text.
Search results can link to images & other files
Choose an item.
Click here to enter text.
Easy navigation between search results, search
items and back to search results
Ability to get a set of code maps supported by the
service? (e.g., Name, OID-source, source code
system name, version using in map, target code
system, OID target etc.)
Other
Additional features
Choose an item.
Click here to enter text.
Additional comments
Click here to enter text.
Click here to enter text.
4.2.9 Part 9 – Cost Structure
Please provide a price list or pricing structure
of your solution. :
Enterprise license cost
Ongoing maintenance and support
Specific development hourly rate
(You may include this as a separate attachment
to this RFI)
Click here to enter text.
4.2.10 Part 10 – Past Projects and References
Please describe at least one previous successful Click here to enter text.
projects.
Please describe at least one previous successful Click here to enter text.
project that is similar in scope and
requirements to the stated project.
Average time vendor projects performed in the Click here to enter text.
past
Israel Health Terminology Project - RFI
Page | 23
4.2.11 Part 11 – Implementation and Support
Time required for initial installation and
configuration
Estimated time to implement – work days and
calendar time.
Resources required for initial installation,
specify also types of resources
Maintenance guide
Click here to enter text.
Operating documentation
Click here to enter text.
Training documentation
Click here to enter text.
User documentation
Click here to enter text.
Telephone service provided
Click here to enter text.
Chat and email service provided
Click here to enter text.
Support hours (please specify time zone)
Click here to enter text.
Guaranteed response time
Click here to enter text.
Maximum time to implement an emergency
Click here to enter text.
Documentation updated for any fixes
Click here to enter text.
On-Site expertise available when required
Click here to enter text.
Service Level Agreement
Click here to enter text.
Warranty: Typical warranty period and the
types of problems covered by the warranty,
Conditions that make a warranty void.
Agreements and services such as help desk
that are available after the warranty period
Routine maintenance activities that must be
performed to keep the product up to date.
Click here to enter text.
Israel Health Terminology Project - RFI
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Page | 24
4.2.12 Part 12 – Consultation
As an experienced vendor in the market, the Israeli Ministry of Health welcomes your
input on the technological issues that are under consideration:
4.2.12.1 MDM products vs. Terminology Server products
It has been suggested that instead of acquiring a TS product, the IMH can use an
MDM (Master Data Management) product such as SAP MDM, Tibco MDM,
Riversand etc. Please provide your opinion on the key differences between the two
solutions, preferably in the format of a comparison table.We may need a combined
solution
4.2.12.2 Managing catalogues vs. managing terminology
The IMH is deliberating if and how to manage the National catalogues (such as
pharmaceuticals and laboratories) as part of the National terminology server project,
or as a separate project / system. Please share your experience and
recommendations on this question, specifying pro's and con's of both alternatives.
4.2.12.3 Managing National terminology vs. providing a National platform
The IMH is considering if it should focus on managing the terminology itself, and
provide the Israeli Health System Institutes with the datasets, or enable each institute
to use the terminology server itself, to manage its specific terminology set mapped to
the National terminology. Please share your view on the implications of each option
for the technical implementation of the National TS.
Israel Health Terminology Project - RFI
Page | 25
4.3 Appendices
4.3.1 Appendix 1 – Partially Supported or Non-Supported Requirements
For each requirement that is either "Not Supported" or "Partially Supported" Please
state how many man days of work are required in order to fully complete this
feature if you intend or are otherwise considering adding this feature. You may add
any additional comments as necessary.
Feature
Click here to enter text.
Work Required
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Israel Health Terminology Project - RFI
Page | 26
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Click here to enter text.
Israel Health Terminology Project - RFI
Page | 27
4.3.2 Additional Comments
Please add any additional comments or notes that you wish to bring to the attention of the
requesting parties here.
Click here to enter text.
Israel Health Terminology Project - RFI
Page | 28