04-15-21 RFP

a. Design package: The Contractor shall include State’s Solutions Architecture Team (“SAT”) in
design discussions and shall:
(1) Organize and conduct design sessions with subject matter experts to identify the
necessary configurations, system design for reports and interface development
(2) Provide input and conform to the direction of the State enterprise architectural standards
(3) Collaborate with State technical resources and SAT for successful compilation of Solution
Design Package (“SDP”). SDP shall contain design documentation for successful system
deployment such as system infrastructure, data classification, audit, disaster recovery
and operational requirements
(4) SDP documentation is maintained by STS for the life of the System and the Contractor is
responsible for providing the necessary updates before implementation and in the
Maintenance and Operations phase (see Section A.18) as needed

b. Configurations: The Contractor duties for the System configuration shall include but are
not limited to:
(1) Engaging the subject matter experts and utilizing sandbox environment for configuration
sessions
(2) Utilizing State specific business terminology to the extent possible for configuration of
modules, alerts/notifications
(3) The Contractor shall submit Technical Specification Deliverable for State approval
discussing the necessary configurations, design, and development of interfaces

c. User access management: The Contractor shall implement active directory authentication
and design role-based access control to the System and provide assistance in developing
procedures for configuration of new users, and user account management based on staff
changes.

A.6. Interoperability / Interfaces. The Contractor shall configure or build necessary interfaces to ensure
that the EHR solution interoperates with necessary systems including but not limited to those
listed in the table below. Interoperability details and specific implementation standards that are
expected to be supported for specific use cases are included. Additionally, the Contractor is
expected to support US Core Data for Interoperability (USCDI), and all vocabulary and
terminology standards referenced by the interoperability standards and the USCDI including but
not limited to ICD-10, SNOMED-CT, LOINC, CPT, NDC, CVX, RxNorm, NCPDP and associated
value sets like those published by HL7, and the 2015 Edition certification criteria, 2015 Edition
Cures Update certification criteria, or a combination of both.

The Contractor shall meet the various interoperability use cases required by federal regulation,
including but not limited to:
a. An unsolicited “push” of clinical health information to a known destination and information
system (for additional information see HealthIT.gov Services/Exchange)
b. Transport for transition of care or referral to another health care provider communication
between providers external and internal treatment (for additional information see
HealthIT.gov Transitions of care)

Interfaces include but are not limited to:

System Name Description Data Flow HL7? Implementation

(Bi-Directional, Details
Input, Output)

TennIIS EHR would check Bi-Directional Yes Centers for

immunization records in Disease Control
TennIIS, and results are and Prevention
returned including forecast, (CDC) Health
Level Seven

9
 04-15-21 RFP

System Name Description Data Flow HL7? Implementation

(Bi-Directional, Details
Input, Output)
updates would be sent to (HL7) Version
the IIS. 2.5.1
Implementation
Guide for
Immunization
Messaging
Release 1.5,
10/01/2014
(CDC IG)

HL7 Version
2.5.1
Implementation
Guide for
Immunization
Messaging
Release 1.5 –
Addendum,
07/2015
(Addendum)

2.5.1 QBP and

RSP Technical
Specifications for
the Tennessee
Department of
Health (TDH)
Immunization
Information
System

2.5.1 VXU and

ACK Technical
Specifications for
the Tennessee
Department of
Health (TDH)
Immunization
Information
System

CDC WSDL
The link to the
CDC website
with technical
specifications
and details about
the CDC WSDL:
https://www.cdc.
gov/vaccines/pro
grams/iis/technic
al-
guidance/soap/s
ervices.html

10
 04-15-21 RFP

System Name Description Data Flow HL7? Implementation

(Bi-Directional, Details
Input, Output)

TNWIC - Registration information is Bi-Directional Yes

Registration sent to TNWIC and an
acknowledgement is
received. (Demographic
sent to TNWIC)

TNWIC - Appointment information is Bi-Directional Yes

Appointments sent to TNWIC and a
message is received back
to confirm an appointment
has been made.

TNWIC - Measures TNWIC to query the EHR Bi-Directional Yes

(Query and response).

Pharmacy Sending of electronic orders Bi-Directional No NCPDP-

for pharmacy prescriptions SCRIPT

POS Pharmacy Point of sale for direct Bi-Directional No

pharmacy billing

POS (Administrative Point of sale for services Bi-Directional No

Revenue) rendered

Lab - LOI Submission of a Laboratory Bi-Directional Yes HL7 Version

Order to the Lab. Need to 2.5.1
have the ability to send Implementation
order cancellation requests Guide:
and order updates. Likely Laboratory
receive Lab order ACKs. Orders (LOI)
from EHR,
Release 1, - US
Realm
Lab - LRI Receipt of a Lab Result, Bi-Directional Yes HL7 Version
including preliminary, final, 2.5.1
and corrected results, as Implementation
well as accommodate reflex Guide:
testing. Likely send ACKs. Laboratory
Results Interface
Release 1 – US
Realm
Lab Compendium Receipt of a Lab Input Only Yes
Compendium of tests from
the Laboratory, including
necessary metadata and
coding for various concepts,
like order codes, test codes,
result codes, specimen
codes, AOE questions and
coding

11
 04-15-21 RFP

System Name Description Data Flow HL7? Implementation

(Bi-Directional, Details
Input, Output)

Surveillance Sending of electronic case Output only Yes

reports to integrated (future potential HL7 CDA® R2
disease surveillance system for bi- Implementation
directional) Guide: Public
Health Case
Report, Release
2: the Electronic
Initial Case
Report (eICR),,-
US Realm

Related
Standards:
HL7 FHIR®
Implementation
Guide: Electronic
Case Reporting
(eCR), Release
1 - US Realm

HL7 CDA® R2
Implementation
Guide:
Reportability
Response,
Release 1 - US
Realm
CSMD Send query for patient Bi-Directional No 2 Methods:
Controlled Substance 1) Appriss
prescription info and receipt Gateway
of findings from the CSMD.
2) RxCheck EHR
connectivity
MPI Send queries and receive Bi-Directional Yes
responses, send updates

Medical Current TDH Clearinghouse Bi-Directional Yes Attachment C

Clearinghouse that provides insurance includes
eligibility information and requirements for
submit claims for payment the EHR to
and receive response. include medical
System creates HIPAA clearinghouse
compliant EDI transactions functionality. If
for the electronic the requirements
submission of claims cannot be met,
interoperability
will be required.

A.7. Data Migration. The State and the Contractor shall actively collaborate to determine the data
migration needs and strategies.

a. Data Migration-Contractor Responsibilities. The Contractor’s responsibilities shall include, but

are not limited to:

12