36C10B19R0014-011.docx

ATTACHMENT A: SUSTAINMENT OF VDIF EP CORE COMPONENTS

Figure 1: VDIF Enterprise Platform (VDIF EP) Components – (shaded blue section indicates main VDIF EP Components).

Regional Preload

HealthShare Enterprise Platform

(HSEP)

Preload Health Connect

VistA Namespace

Information Exchange

Audit Repository HS Instance

ATNA

Audit Repository Production

Audit Repository API

VPR Package

VistAVistA

Service Bus Health Connect (Future)

Advanced Medication

Platform (AMPL) Pharmacy GUI (Future Integration)

Service Registry (Runtime endpoint management)

(Design Time Discovery, Governance)

IHE Bus

Interfaces

XSLT, SDA

Extensions

Edge GatewaysEdge GatewaysEdge GatewaysEdge GatewaysEdge Gateways Edge Gateway HS Instances

Namespaces

SDA Extensions

ECR

VHIE

CDA

Legend

Data store

VA Specific Classes, etc.

HealthShare native interfaces

Service proxy eHX Adapter

Master Veteran Index

VETS (Future: CTT&DM)

VAAFI SOAP

Mutual

TLS

Regional

APIs & Tables

Extract Load & Integration

Services

Regional

Regional HealthShare HealthShare/HealthConnect (HS/HC)

Regional HL7 Router

Regional Router

Rules, Process

Region Specific Hosts/Config.

Regional Router

HealthConnect (HC)

HL7 Messaging HealthConnect

National HL7 Router

Rules, Process, Business Hosts

HL7

VistAsVistAs Devices (PADE devices, etc.)

FHIR Gateway

FHIR Gateway

VA FHIR

FHIR API

<<FileMan File>> File #1.5

<<FileMan File>> Protocol File

<<Global>> Data Change Event Global

VistA Application PackagesHL7

Enterprise HL7 Consuming

Systems (ECMS, etc.)

DRAWN BY

Travis Hilton

TITLE

VistA Data Integration and Federation Enterprise

Platform (VDIF-EP) Production Ready at AITC

REVISED

1/10/2019

DESCRIPTION

This view illustrates an SV-2 overview for the

“HSE VistA Data Federation Production Ready at

AITC” step of the HSE Platform Architectural

Roadmap. Its intended audience is the IT

Operations team, who is expected to created detailed deployment diagrams using this diagram as a guide.

VERSION

0.40

VIEW

SV-2 Systems Resource Flow Description -

Overview

Acronyms

AITC – Austin Information Technology Center AMPL – Advanced Medication Platform CCRA – Connected Care Referrals and Authorizations CTT&DM – Clinical Terminology Tooling & Data Management ISAAC - InformaticS Architecture ACceleration) subsystem DR – Disaster Recovery ECR – Edge Cache Repository ETTS - Enterprise Terminology Tooling System FHIR - Fast Healthcare Interoperability Resources GUI – Graphical User Interface HA – High Availability HC – Health Connect HSE – HealthShare Enterprise HSRM – HealthShare Referral Manager KOMET – ETTS Terminology Editor RDC – Regional Data Center PITC – Philadelphia Information Technology Center SSOe – Single Sign On for External Users SSOi – Single Sign On for Internal Users TIC – Trusted Internet Connection VAMC – VA Medical Center

CONNECT

Gateway

VAP

Chemotherapy Order

Management System (COMS)

X12 Messaging

National X12 Router

Rules, Process, Business Hosts

Enterprise EDI Consuming

Systems (EDI clients)

X12

Corporate Data Warehouse (CDW)

Mechanisms VPR Get

Patient Data API

Data (SDA)Invoke

GUI

Patient Data Update Push Mechanism

(SDA)

Updates

Write-back APIs

Change Events

(ECP)

VPR Get

Data API

(ECP)

Data

VA External SMART on FHIR Clients

(e.g. Apple Health App)

Lighthouse

FHIR API Proxy

FHIR Resources (Read)

Aggregated/De-duplicated Patient Data

Data Read

External Partners

VHIE Audit Log

Data Access Service

(DAS)

Received CDAs

Protocol File Event

Listeners

Vista Globals

Metadata Object Store ???

Audit Records

FHIR Session Cache

Access Gateway

Clinical Viewer Interfaces

SDA

FHIR API

Write

Access Gateway

SDA

Administration and Reporting

Application

Reports/Analysis

Document Repository

XDS.b Doc. Repository

Document Repository API

Registry

Registry

Consent Policy, Registries, Subscriptions.

Patient Registry

Code Sets

Patient DFN

Audit DB

CDA DB

ESR

Secondary

Demographics

Audit Adapter

Still under evaluation for inclusion on this step

Represents a virtual machine candidate

Future integration (after this step has been deployed to production

Exception Handling:

First detect Mumps routine failures in the VPR Get Patient Data API routines

VPR must resolve missing coded value descriptions where appropriate by calling the local Lexicon APIs that look up the descriptions

Exception Handling:

Type cast errors for on the wire SDA to

Cache Object ingestion detected here.

Queue Fixed Data

When VistA data is corrected due to a DQ issues, a mechanism is created to add a data change event to the global so that it gets re-loaded into the Edge Gateway

Write-back

Application Access Control (Authentication &

Authorization of Application + Audit)

Application Access Control (Authentication &

Authorization of Application + Audit)

(Write)

Terminology Content Management Tools and Services (e.g. ISAAC, KOMET, ETTS, etc)

Generated CDAs temporary store

CTT&DM

Terminology Mapping

Web Service (VETS replacement)

Issue: Performance concerns for Phase I due to calls to ESR for every request. Register interest and caching for

Phase II will alleviate the performance hit.

Terminology Mappings via

SOAP

Terminology Maps

Mapping Profiles

Terminology Mappings and Code Sets

X

New HL7 Integrations

New Enterprise HL7 integrations can bypass the

Regional HL Router going forward in an effort to reduce the number of hops.

Vista Integration Adapter (VIA)

(Future Integrations –

BMS, NUMI, VCL,

MyHealthVet,+24 more)

Cerner

Cerner HIE DoD

CommVault Regions 2, 3 and 4

Backups

CACHE.DAT

SFTP Region 1

Backups

CACHE.DAT

Install

Primary

Demographics, Correlated Ids, Facility Ids, ICN

HSEP VistA Data Federation Production Ready at AITC SV-2 Overview 20190109 v40.vsd

SV-2 Overview image1.emf