ATTACHMENT H - BAR Mapping Journal_v6.10_202106.pdf

Feb 2021 version 6.9 P a g e | 1

Veterans Health Administration (VHA)

Office of Health Informatics (OHI)

Strategic Investment Management (SIM)

Business Architecture (BA)

Integration and Reference (IR)

Mapping Journal

Version 6.10

June 2021

OHI:

SIM:

BA

IR Mapping Journal

Introduction

June 2021 Version 6.10

Revision History

Date Version Description

September 13,

0.1 Initial draft started

November 20,

0.2 Contractor reviewed

November 20,

1.0 Version 1 created

February 5, 2018 1.1 Initiated work for Version 2.0

February 20,

2.0 • Added section M31 HL7-HER System Function BFF

• Changed M36 section title from “MYP Investment Requests (Plans) to BFF” to “MYP Business Cases to BFF”

• Changed organization names:

- From Business Reference Architecture (BRA) to Integration and Reference (IR)

- From Business Information Architecture (BIA) to Business Information and Knowledge (BIK)

- From Business Process Architecture (BPA) to Business Process and Value (BIV)

• Other minor edits include formatting and dates

April 16, 2018 2.1 • All references to the SPA (Strategic and Performance Architecture) unit are changed to Strategy and Planning (SP)

• All references to the BIV is corrected to BPV (Business Process & Value

• In Section M1, on Page 4, under History, Typically Updated, removed “more” from “The ONC FHIT Strategic Goals are more not updated at the same frequency as the HISP.”

April 19, 2018 2.2 These changes are direct results of comments received during the Mapping Journal Demo presented at the BA POC Online Meeting on 4/18/2018.

• Standardize wording under “Typically Updated” in the “History” sections o “Every BAR Release” instead of “Every BAR”, or o “When [update trigger]”

• Footnote “Engineering judgement is the ability to perform analysis and reach a conclusion based on domain knowledge of the analysts and contributors.” Is added.

May 2018 3.0 • Moved R&A VHA IT Business Needs to OMB 300 – Available Upon Request to section Archived Mapped Product

• Moved VHA Exhibit 53 to BFF – Available Upon Request to section Archived Mapped Product

• Moved VHA Priorities for Strategic Action to VHA Health IT Goals to section Archived Mapped Product

• Moved VHA Priorities for Strategic Action to VHA HIT Improvement Opportunities to section Archived Mapped Product

• Added the following mapped products to Volume I: Strategy o VA Top 5 Priorities to VHA Health IT Goals o VA Goals and Objectives to VHA Health IT Goals o VHA HIT Improvement Opportunities to VHA Health IT Goals o VHA HIT Improvement Opportunities to VA Top Priorities o VA Top 5 Priorities to VHA BFF o VA Goals and Objectives to VHA BFF

• Added the following mapped products to Volume V: Security & Privacy o HIG S&P Solutions Based Architecture to Goals and Priorities

• Added VistA Application Files, Fields and Package Menu Items Lists – Available Upon Request to section Other Mapped Products

• Updated M39 VA Application List to BFF to include expansion to the original mapping protocol

August 2018 4.0 • Added the following mapped product to Volume II: Business o VHA Business Process Global Tasks to BFF

• Added the following mapped product to Volume III: Business Priorities, Requests and Requirements o RDM Sub Epics Referenced by RDM Epics

• Added the following mapped products to Volume IV: Business Applications o VHA Purchased Cerner Solutions to BFF o VHA Purchased Cerner Solutions to Primary Business Capability

• Added Preliminary Analysis of VASI Legacy Systems to be replaced by Cerner Solution Modules – Available Upon Request to the Other Mapped Products section

• Updated M12 VA Business Reference Model to BFF to include the new VA BRM version

November 2018 5.0 • Changed VHA HIT Improvement Opportunities to VHA Health IT Goals to VHA HIT Goals and Objectives to Health IT Strategic Drivers

• Changed VHA HIT Improvement Opportunities to VA Top 5 Priorities to VHA HIT Goals and Objectives to BFF

BA

Date Version Description

February 2019 6.0 • Reorganized sections to match new BAR Segment Workbooks

May 2019 6.1 • Updated sections where BAR Segment Workbooks changed names and order of mapping tabs

• Added to Volume HISP M4C VHA Health IT Goals and Objectives to VHA Priorities

• Updated Guidelines for IT Systems M1 VA Application List to BFF

• Archived 8 EHRM mappings

Aug 2019 6.2 • Changed language from segments to topics

• Moved 89 tabs archived per BAR Review Assessment to either ‘Other Mapped Products – Available on Request’ where they were identified for internal use or to ‘Archived Mapped Products’ otherwise. Removed pivot and reverse pivot tabs.

Nov 2019 6.3 • Updated for Nov BAR – Added 2 Reports into the BAR of which were Archived in August. Note– Diff Tabs in BAR Directory for NOV release

R23 -VHA Clinical Service Lines

M23 -VHA Clinical Service Lines to BFF

• Added archived BAR TABS from Aug where updates not previously incorporated.

• Built content for each of the following: (EHRM Archived.

• All preceded by E-RM1A, M1B, M1C, M2A, M2B,M3B,M6B,M6C) Note: These were renamed in May BAR Release. Note in Historical Reference on BAR shows names and tabs with

Aug Newly Named Tabs and reflects were Archived as part of the consolidated BAR process accomplished in Aug BAR release.

Feb 2020 6.4 • Version, Date on Cover page and footers updated

May 2020 6.5 • Updated: (Header/Footer updates; Content updates applied; Diagram in Introduction replace with current mapping list.

• Updated Content to reflect Archived Reports: OPS-M4 VHA Clinical Programs to VHA BFF

• OPS-M9 VSSC Clinical Measures to VHA BFF

• OPS-M6A VHA Medical Facilities to Clinical Programs

• OPS-M6B VHA Medical Facilities to VHA Clinical Service Lines

Sept 2020 6.6 • Updated: (Header/Footer updates; Content updates applied; Diagram in Introduction replace with current mapping list.

• Updated TOC and Section headings to reflect VHA BFF where applicable.

• Verified all data in TOC entries were reflected in this document with exact names as TOC reflects.

• Added back – Informational content of “M16A VHA HIT Goals and Objectives to Health IT Strategic Drivers”.

Oct 2020 6.7 • Updated M9 Name Change & date heading updates

Nov 2020 6.8 • Updated to reflect updates for R20, M20A and M20B; Removed Data updated per Central Office reorg. Column 'Part of May 2017 Data Call?

February 2021 6.9 • Updated to reflect addition of M20C

June 2021 6.10 • Changes to Mapping number schema for BAR Tabs, M20, M21A, M21B, M21C, M22, M23, M24 , these were due to M13 being moved under section HIG in BAR workbook. Updated to reflect Business Function Framework 3.7 impact. BC to BFF, BS to BFF, BPM to BFF, BPOA to BFF, Org Roles to BFF, Goals and Objectives to BFF, Priorities to BFF, Health IT Goals to BFF, VASI to BFF, HIG SPFM to BFF, Central Office Ort to BFF, VISN Ref Org to BFF, Med Ctr Ref Org Model to BFF, Clinical Service Lines to BFF.

BA

Contents

Introduction

Guideline Structures

Update Cycle

Topic I: Alternative Reference Models

M1 iBRM 2.0 to VHA BFF

M2 VA Business Reference Model to VHA BFF

Topic II: Core Business Architecture

M5 VHA Business Capabilities to VHA BFF

M6 VHA Business Services to VHA BFF

M7A VHA Business Process Model Names to VHA BFF

M8 VHA Business Process Operational Activities to VHA BFF

M9 VHA Organizational Roles Model to VHA BFF…………………………………………………………………..….18

M10 VHA NDO Business Process Context and Traceability

M20 Health Information Governance (HIG) Security & Privacy Functional Model (SPFM) to VHA BFF

Topic III: HISP

M14A VA Goals and Objectives to VHA BFF

M14B VA Goals and Objectives to VHA Health IT Goals

M15A VA Priorities to VHA BFF

M15B VA Priorities to VHA Health IT Goals

M16A VHA HIT Goals and Objectives to Health IT Strategic Drivers

M16B VHA Health IT Goals and Objectives to VHA BFF

Topic IV: IT Systems

M18 VA Application List (VASI) to VHA BFF

M19 VHA HIG S&P Solutions Based Architecture to Goals and Priorities

Topic V: VHA Operations

M21A VHA Central Office Organizational Offices Model to VHA BFF

M21B VHA Central Office Organizational Model to VHA BC

M21C VHA Central Office Organizational Model to FOM

M22 VISN Reference Organizational Model to VHA BFF

M23 VA Medical Center Reference Organizational Model to VHA BFF

M24 VHA Clinical Service Lines to VHA BFF

Other Mapped Products – Available Upon Request

BA

BUSINESS CASE RELATED – Available Upon Request

VHA IT Governance - Capability Management Boards to VHA BFF

MYP Business Cases to Applications

MYP Business Cases to VHA BFF

MYP Business Cases to VSSC Clinical Measures

M5A IKM VHA IT Business Needs to RDM Business Needs

M5B IKM VHA IT Business Needs to RDM NSRs

Legacy VistA Menu Items to HL7-EHR System Functions

EHRM RELATED – Available Upon Request

Cerner Solution Modules that support each Business Capability

Cerner Solution Modules that support each Business Function

Cerner Solution Modules that support each Business Service

Preliminary Analysis of VASI Legacy Systems to be replaced by Cerner Solution Modules

Cerner Workflows that support each Business Capability

Cerner Workflows that support each Business Function

VHA Subsets of Care aligned to EHR Councils

EHR Council(s) to have a likely interest in Cerner Solution Modules

EHR Councils likely to have primary responsibility for Cerner Workflows

EHRM Capability Requirements to VHA Business Capability

EHR Councils to s and Related Business Capabilities

EHR Councils to s to Supported Business Functions

EHRM Capability Requirements to VHA Business Functions

HISP RELATED – Available Upon Request

VHA HIT Goals and Objectives to VHA Priorities

NSR RELATED – Available Upon Request

RDM IDRP Requests to VHA BFF

VISTA APPLICATION RELATED – Available Upon Request

VistA Application Standard Files and Fields

VistA Application Files to VistA Packages

VHA MONOGRAPH RELATED – Available Upon Request

VHA Monograph to VASI

VHA Monograph to BFF

VHA OPERATIONS RELATED – Available Upon Request

Preliminary Analysis of VASI Legacy Systems to be replaced by Cerner Solution Modules

Archived BAR Mapped Products

STRATEGY/HISP RELATED

ONC Federal Health IT (FHIT) Strategic Goals to VHA Health IT Goals

Blueprint for Excellence Strategies to VA Strategic Goals & Objectives, HIT Goals, VHA Priorities for Strategic Action

BA

VHA HIT Strategic Drivers to VHA Strategic Objectives

VHA Strategic Objectives to BFF

MyVA Breakthrough Priorities to BFF

MyVA Breakthrough Priorities to VHA HIT Goals

VA Blueprint For Excellence Strategies to BFF

FHIT Drivers to Blueprint for Excellence Strategies

VHA Priorities for Strategic Action to VHA HIT Goals

VHA Priorities for Strategic Action to VHA HIT Improvement Opportunities

CORE BUSINESS ARCHITECTURE RELATED

NDOs with Business Process Models to BFF

BUSINESS CASE RELATED

FY17 & 18 Budgets to FY17 & 18 MYP IT Investment Requests – Available Upon Request

IKM VHA IT Business Needs to OMB 300 – Available Upon Request

VHA Exhibit 53 to BFF – Available Upon Request

EHRM RELATED

All Direct Mappings that align from Cerner Solution Modules

All Direct Mappings from Cerner Workflows

NSR RELATED

NSRs to VHA BFF Directly

RDM NSRs to RDM Business Needs

RDM Business Needs to VHA BFF

RDM Business Epics to VHA BFF

RDM Sub Epics Referenced by RDM Epics

HL7-EHR System Function to VHA BFF

IT GOVERNANCE RELATED

VHA Federal Programs List to VHA BFF

VHA Federal Programs to VA Top 5 Priorities

IT SYSTEMS RELATED

VHA Enterprise Shared Services (WSRR) to VA BRM

E-R-M1ABusiness Capability supported by each Cerner Solution Module

E-R-M1B Business Function supported by VHA Cerner Solution Modules

E-R-M1C Business Service supported by VHA Cerner Solution Modules

E-R-M2A Business Capability supported by each Cerner Workflows

Description

E-R-M3B VHA Cerner Solution Modules of interest to each EHR Council

OPS-M6B VHA Medical Facilities to VHA Clinical Service Lines

OPS-M6C VHA Medical Facilities to VHA Occupational Titles with FTEs

OPS-M6A VHA Medical Facilities to Clinical Programs

OPS-M4 VHA Clinical Programs to VHA BFF

BA

OPS-M4 VHA Clinical Programs to VHA BFF

OPS-M6B VHA Medical Facilities to VHA Clinical Service Lines

CBA-M7B VHA Business Process Model Names to VHA Functional Roles Model

Appendix A: Recommended Mapping Guidelines and Principles

Appendix B: Acronyms

BA

Introduction

As a component of the Business Architecture Repository (BAR), the mapped products are direct relationships between two sets of referenced architecture entities. Some of the mappings are based on analysis by the Integration and Reference (IR) team. Some mappings are provided by other teams and/or in conjunction with the IR.

Figure 1 – Mapped Products in the Business Architecture Repository

When mapping analyses are performed, the analysis teams formulate mapping rules or guidelines specific to the reference sets that are being mapped. These guidelines aid the analysis teams to apply a consistency when determining the appropriate relationships and help users of the mapping products better understand the contained relationships. Once done, the mapping products are typically updated on a regular frequency or upon a pre-determined event.

The BAR Release Notes identify when each mapping product was last updated.

This IR Mapping Journal provides an inclusive log of all protocols and guidelines, which are uniquely utilized for each mapped product. The intention is to capture baseline or updated logical rules and strategies in all mapping exercises being performed collaboratively with various individuals/groups. However, it is not intended to replace the BAR Release Notes.

The benefits of the IR Mapping Journal are:

BA

Guideline Structures

• Standardization and baselining of guidelines

• Normalization of the qualitative analysis of mapping exercises

• Maturity of guidelines logged

• Absorption of lessons learned into guidelines progressing mapping exercises towards optimum efficiency and ability to communicate

• Saving of time and effort in discovery and understanding of mapping guidelines

Guideline Structures

This document leverages a modular design to optimize access and readability, and to simplify document maintenance. This section elaborates on the structure and organization of mapping guidelines document.

The mappings are grouped into volumes reflecting the current BAR topics which were separate

Segment Workbooks for Feb 2019 through May 2019. The volumes are:

• Volume I: Alternative Reference Models

• Volume II: Business Requirements

• Volume III: Core Business Architecture

• Volume IV: EHRM

• Volume V: HISP

• Volume VI: IT Systems

• Volume VII: VHA IT Governance

• Volume VIII: VHA Operations

Following the volumes, guidelines for Available Upon Request and Archived Mapped Products are also included.

Each mapped product within a volume encapsulates the following elements to describe what, who, how and when the new / existing mappings are created / updated.

The Description defines which two or more source artifacts are aligned. It describes linkages between the Business Function Framework (BFF) and other pieces of the business architecture, relationships to One-VA Enterprise Architecture (EA), other agencies, as well as key Veterans Health Administration (VHA) activities and efforts.

BA

Update Cycle

If mapping is the result of a collaborative effort between IR and stakeholders, the Stakeholders section provides a list of stakeholders and how the stakeholders are engaged. This section describes high-level logistics, supplement materials (template spreadsheets, informational / reference documents, etc.), and stakeholders’ roles involved in mapping, and in review. If the IR team is solely responsible for mapping analysis, then the identified stakeholders will be “None”. Thus, this section should not be confused with the stakeholders who might use the finished mapped products.

The Guidelines section discusses the logical framework for the mapping and review exercises. It allows for standardization and normalization in the analysis and serves as the starting point and / or discussion items to streamline the collaboration efforts with stakeholders. The guidelines listed in this section are user-defined, which enables the mapping teams to extend or modify the general mapping guidelines contained the Recommended Mapping Guidelines and Principles.

A common set of Recommended Mapping Guidelines and Principles provides basic recommendations for structuring and performing a mapping exercise to show alignment between components of two or more source artifacts. These guidelines and principles provide suggested best practices and standards for anyone engaging in a mapping exercise (also referred to as users). Iteration of this is in Appendix A.

The History section captures the original mapping date, update frequency, and, if a mapped product has been archived, the archival date.

Update Cycle

The IR Mapping Journal was created in October 2017 and will be a living document going forward. Mapping sets archived prior to the August 2017 BAR will not have journal entries. This document is updated based on needs, and the following occurrences may trigger updates:

• Modifications (addition or removal of mappings) and publications of the BAR,

• Changes in how a data steward may be engaged of they are involved in mapping analysis, and

• Changes in mapping guidelines for a mapping product.

BA

Topic I: Alternative Reference Models

• All mappings to the business function framework were updated to reflect the new and updated functions identified in BFF 3.7 (June

2021)

Topic I: Alternative Reference Models

M1 iBRM 2.0 to VHA BFF

Description

This mapping of Integrated Business Reference Model (iBRM) 2.0 to VHA BFF provides mapping of the BFF to the iBRM v2.0. Developed by the iBRM Working Group under the

Integrated Electronic Health Record (iEHR) Business Process Group governance board.

Stakeholders

The iBRM Working Group, under the direction of the Department of Defense (DoD) / Veteran

Affairs (VA) Business Process Group (BPG), was tasked with the development and continued maintenance of the iBRM in 2013. The iBRM working group was primarily composed of stakeholders from VHA IR and DoD Defense Health Agency (DHA). A mapping between the iBRM and the existing VHA BFF was completed by the joint VHA and DoD working group. Since

2013, the VHA IR team has been responsible for the maintenance of the mappings.

Guidelines

Original

This represents a business function-to-business function relationship of activities originating from separate and unique architecture models. As such, mapping one function to another denotes exact or similar definitions of activities are being performed in each function. It represents a translation of definitions, meaning that both definitions are synonyms of each other. Relationships will be analyzed and documented at the lowest-level item/node as possible.

It is possible that a level 3 node in the iBRM can be related to a level 2, 3 or 4 level business function in the VHA BFF and vice versa.

History

Original Mapping Performed: March 2013

In March 2013, the second version (2.0) of the iBRM was published. Both agencies participated in the original mapping of the VHA BFF to the newly developed iBRM. Since 2013, the VHA IR team has been solely responsible for the maintenance of the mappings as the VHA BFF continues to evolve.

Typically Updated: When the BFF is updated

BA

Note: Refer to BAR Release Notes for specific past update dates

M2 VA BRM to BFF

Description

This mapping of VA Business Reference Model (VA BRM) to BFF provides mapping of VA BRM components to the BFF. The mapping analysis is performed by the VHA IR team.

Note: Prior to March 2017, the VA BRM was the VA Enterprise Capability Model (VA ECM). The

VA ECM referenced the VHA BFF for scope details. When the VA BRM replaced and superseded the VA ECM, the VA BRM contained business function nodes with scope granularity par with the VA BFF.

Stakeholders

None

Guidelines

Original

• VHA BFF leaf nodes are aligned to VA BRM leaf nodes, with the following exception o A BFF leaf node may be mapped to VA BRM summary node if it expresses the scope of BFF leaf node and the VA BRM children provide detail not contained within the VHA BFF

• A VHA BFF summary node may be aligned to a VA BRM summary node if:

o The VHA BFF children leaves have already been mapped to the VHA BRM, and o The VA BRM summary node scope is exactly equivalent to the VHA BFF summary node.

• The relationships represent:

o The VHA business function scope is equivalent to the associated VA BRM business function scope, or o The VHA business function scope is contained within the broader scope of the VA BRM business function.

History

Original Mapping Performed: April 2017

Typically Updated: When BFF is updated or after the VA BRM is updated

BA

BA

Topic II: Core Business Architecture

Topic II: Core Business Architecture

M5 VHA Business Capabilities to BFF

Description

This mapping of VA BRM to BFF displays a mapping from VHA Core Business Capabilities to VHA business functions. The mapping represents which business functions are needed to perform the scope of the core business capability.

Stakeholders

The BA Director’s Office is engaged as a reviewer of the mappings whenever the mapping product is updated.

Guidelines

Original

• Business Capabilities represent wholistic business offerings that serve VHA’s customers or employees.

• A business capability uses one or more business functions to perform the scope of the business capability

• A business function may support one or more business capabilities, but if it does so, it usually is by using different sets of business rules within common business processes.

• In working with each business capability, the question that is repeatedly asked is, “Does that business capability need the business function to perform the business capability?”.

Engineering judgement1 is used as the basis.

• After working through the mapping product from the business capability perspective, a quality control (QC) can be done by looking at Business Functions supported by VHA Cerner Solution Modules and assessing whether the set of business capabilities supported looks appropriate and complete.

• The relationships represent o The business capability uses the business function(s) to perform the business capability, or o The business function supports the business capability(ies)

History

Original Mapping Performed: August 2016

1 Engineering judgement is the ability to perform analysis and reach a conclusion based on domain knowledge of the analysts and contributors.

BA

Typically Updated: When the BFF is updated, or when the Business Capabilities reference is updated

M6 VHA Business Services to BFF

This mapping of M6 VHA Business Services to BFF displays the business functions that are enabled by each of the business services.

Stakeholders

The BA Director’s Office is engaged as a reviewer of the mappings whenever the mapping product is updated.

Guidelines

Original

• Business Services deliver work results that supports a business, but not necessarily a tangible commodity in and by itself. Business services are cohesively coupled as service systems in order to deliver value within the context of business functions and business processes.

• A business function uses one or more business services to perform the business processes of the business function.

• A business service may support one or more business functions, but if it does so, it usually is done using different sets of business rules.

• In working with each business function, the question that is repeatedly asked is, “Does that business function need the business service in order to perform the business function?”. Engineering judgement1 is used as the basis.

• After working through the mapping product from the business function perspective, a QC can be done by looking at each business service and assessing whether the set of business functions supported looks appropriate and complete.

• The relationships represent o The business function uses the business service(s) to perform the business function, or o The business service supports the business function(s)

Original Mapping Performed: August 2016

BA

Typically Updated: When the BFF is updated, or after Business Services reference is updated

M7A VHA Business Process Model Names to BFF

This mapping of VHA Business Process Model Names to BFF Displays the business function that relate to each Business Process Model. Analysis performed by the Business Process &

Value (BPV) unit in collaboration with the Integration & Reference (IR) unit. The modelers who developed a process model identify the related business functions when the model is completed. The IR unit reviews these mappings in collaboration with the BPV team. Once an agreement is reached on the applicable mappings for a process model, they are documented in the Process Model Summary Report (PMSR) prepared by the BPV team. The IR team uploads the same mappings into architecture tools that track mappings for all business process models.

Only mappings from business process models in a Complete/Approved state are displayed.

Stakeholders

The individual business owners and their designated subject matter experts (SMEs) work with the BPV team to develop process models. They provide information to the BPV team on the specific business process and review and approve the process models. This knowledge of the process is used by the BPV team to identify the applicable BFF mappings. If there are questions on the appropriate mappings for a process model, the BPV team consults the relevant SMEs to gain their perspective.

Guidelines

Original

The IR and BPV teams jointly maintain modeling guidelines for this mapping. The following guidelines apply to the mapping:

• All completed and approved process models should have mappings. Parent processes and their sub processes are each mapped individually.

• Mappings are not inherited. Only map to business functions that are actually shown in the process, do not cascade mappings down from parent processes. This means you should be able to see activities or data objects that illustrate how a mapped business function is provided in the specific model that is mapped. Each mapping implies that the mapped business function is used in the specific process model. For Example: A parent process for ordering medications has a sub process that shows very specifically how a provider evaluates and responds to a drug-drug interaction warning. The child process shows the ordering-related activities and/or data objects. The sub process would be mapped to "Monitor Documentation of Clinician Response to Decision Support

BA

Prompts", but not to "Manage Orders" which would only be mapped to the parent process model.

• Mapping should identify business functions that the process is using, providing, and consuming. When you look at a process that is mapped, you should be able to see the mapped BFF in the process in some way. Some examples are:

o An activity in the model directly provides that business function o An activity in the model uses the business function to conduct the activity

• Map to the lowest BFF required to uniquely identify the function. Do not map to the Line of Business (LOB) level (1.0, 2.0, etc.) except as a last resort. Map at least one level below or lower.

• The goal is to map to the most granular level feasible.

• Mapping to a parent BFF with children is okay, if it is the best mapping (there is no requirement to go to the leaf node in the BFF). Specifically, if mapping to a parent BFF that has children, that means one of three things:

o All children of the parent BFF apply and are shown.

o The level of detail of the model is enough to see the parent BFF.

o If the parent function is the most appropriate mapping and the appropriate child function is not available, then map it to the parent and identify to IR as a possible BFF gap.

• If only some of the children of a BFF apply, then the specific children are mapped, the parent is not mapped.

• Number of mappings o The goal is to have at least one mapping per process model. The number of very strong relationships from process to function is what should drive the ultimate number of mapping. Strong mappings relate to core functions and purposes of the model. Do not make a laundry list of every possible mapping.

o If there is not at least one appropriate BFF mapping, this could point to a gap in the BFF. Leave the process unmapped and discuss with IR as a possible BFF change request.

o More than one mapping is okay within reason. Keep in mind the purpose of the mapping. It is to allow finding functions that support a process or processes that involve a function.

• Avoid mapping to a function that is minimally related to the core function and purpose of the model.

• External producers of business architecture products should inform the BA Team when mappings are created.

Original Mapping Performed: 2013

BA

Mappings are performed whenever a new process model is developed as part of a modelling work effort by the BPV team.

The first mappings of process models to the BFF were performed in 2013. The December 2013

BAR release included initial mappings to over 1400 process models.

Regular mapping review process established with BPV team in 2016. Began weekly meetings to review any new models developed and discuss BFF mappings issues.

Completed full mapping of all Business Process models in the August 2016 BAR release. All

Business Process models in a completed/approved state are mapped to at least one BFF.

Typically Updated: When the BFF is updated and when new business process models are added to the BAR

M8 VHA Business Process Operational Activities to BFF

Business Process Operational Activities (formerly called Global Tasks) perform some aspect of a business function. This report displays which business function each operational activity contributes to the performance thereof. Analysis performed by the Business Process & Value

(BPV) unit in collaboration with the Integration & Reference (IR) unit.

Stakeholders

• BPV Unit and IR Unit

Guidelines

Original

The IR and BPV teams jointly maintain the guidelines for this mapping.

• All completed and approved operational activities should have mappings. Parent processes and their sub processes are each mapped individually.

• Mappings are not inherited.

• Mapping should identify business functions that the task is using, providing, and consuming. When you look at a task that is mapped, you should be able to see the mapped BFF in the task in some way.

• Map to the lowest BFF required to uniquely identify the function. Do not map to the Line of Business (LOB) level (1.0, 2.0, etc.) except as a last resort. The goal is to map to the most granular level feasible.

BA

History

Original Mapping Performed: February 2018

Typically Updated: When the BFF is updated and when new Operational Activities are added to the Rational Software Architect.

M9 VHA Organizational Roles Model to VHA BFFDescription

This mapping of VHA Organizational Roles Model to BFF shows a list of the Business Functions where the mapped VHA Organizational role participates.

This mapping provides an additional organizational perspective to the VHA BFF.

Stakeholders

The IR team updates and maintains this mapping. Stakeholders were not engaged to develop this mapping.

Guidelines

Original

• All organizations in the VHA Organizational Roles should have mappings. Parent roles and their child roles are each mapped individually.

• Mappings are not included in an inherited. Only map to business functions that relate to the specific VHA Organizational Role, do not cascade mappings down from parent roles to their children roles. Do not roll-up mappings from children to the parent.

• Map to the lowest BFF required to uniquely identify the role. Do not map to the LOB level

(1.0, 2.0, etc.) except as a last resort. Map at least one level below or lower.

• The goal is to map to the most granular level feasible.

• Mapping to a parent BFF with children is okay, if it is the best mapping (there is no requirement to go to the leaf node in the BFF). Specifically, if mapping to a parent BFF that has children, that means one of the following possibilities:

o All children of the parent BFF apply and are shown.

o The level of detail of the model is only enough to see the parent BFF.

o If the parent role is the most appropriate mapping and the appropriate child function is not available, then map it to the parent and identify to IR as a possible

BFF gap.

• If only some of the children of a BFF apply, then the specific children are mapped, the parent is not mapped.

BA

History

Original Mapping Performed: February 2016

This mapping was first included in the BAR in February 2016. Business Functions were mapped to the relevant VHA Health Roles, which was a forerunner for the VHA functional Roles. As the model evolved to the VHA Functional Roles model, these mappings were maintained.

Typically Updated: Every BAR Release if there are new VHA Functional Roles identified during that quarter, or when the BFF is updated. The functional roles was changed to Organizational

Roles in Oct 2020 BAR Release.

M10 VHA NDO Business Process Context and Traceability

For work efforts where Process Data Objects were analyzed, this shows the associations between Business Data Objects and Business Activities found in a Business Process Model. It also shows additional information from the analysis that is used to identify Normalized Data

Objects (NDOs) in a Business Process. Source of data is Business Information & Knowledge

(BIK) unit.

A mapping from NDOs to business process models means that there is at least one data object in the process model that is an instance of the mapped NDO. The BIK team tracks more specifically, for each Business Process Model with mappings, which data object is mapped, as well as the activity or gateway in the process model that is associated with the specific data object.

Stakeholders

The BIK unit is the content owner for the mappings of NDO to business process models. They maintain the NDO Traceability Spreadsheet which tracks all NDOs developed by BIK. The IR team incorporates updates to the NDO Traceability sheet into the BAR for each release.

Guidelines

Original

The BIK team maintains the guidelines used to develop the NDO traceability sheet. These guidelines are incorporated into their information modeling guidance document which is available on SharePoint. The IR team takes the content from BIK without further modification.

BA

Topic III: HISP

History

Original Mapping Performed: November 2014

This mapping was first included in a BAR release in the November 2014. The BIK team had previously performed these mappings, but they were not published in the BAR.

The IR team piloted publishing additional data about the mapping in BAR releases in 2016. This data included additional mappings from the BIK NDO Traceability Spreadsheet, such as:

Business Activity, Process Model Data object and Direction of Association. This content was discontinued in the February 2017 BAR release and made available only on request from the

BIK team. The Troux Architecture tool used for BAR release at this time did not have the capability to capture the details of this relationship and the data was not in a format suitable for presentation.

Typically Updated: When the BFF is updated

Note: Refer to BAR Release Notes for specific past update dates

Topic III: HISP

M14A VA Goals and Objectives to VHA BFF

Description

This mapping of VA Goals and Objectives to the VHA BFF shows the link between each VA

Goal and Objective to the relevant business functions in the VHA BFF.

Stakeholders

Stakeholders are the BA SP unit and IR (IR did the mappings). The primary stakeholder for this mapped product is SP. The SP team works directly with IR to identify and documents the linkage between each VA Goals and Objectives and the VHA BFF. Mappings were developed by IR and reviewed by S&P.

Guidelines

Original

• Each VA Goal was mapped to the relevant Objective.

o For example, VA Goal 1 was aligned to VA Objectives 1.1 and 1.2.

• The objectives were then mapped to the VHA BFF.

• For example, VA Objectives 1.1 and 1.2 were mapped to all of LOB 3 as the objective states, VA anticipates Veterans’ changing needs throughout their lives to enhance their choices.

BA

o This objective reflects VA Goal 1.

o Therefore, LOB 3 Provide Health Care Administration is applied.

History

Original Mapping Performed: May 2018

Typically Updated: As needed

BA

M14B VA Goals and Objectives to VHA Health IT Goals

Description

This mapping of the VA Goals and Objectives to the VHA Health IT Goals provides the mapping of all four goals their respective objectives to the VHA Health IT Goals.

Stakeholders

Stakeholder for this mapping is the BA SP unit. The SP team analyzes the contents and premise of the source primitives and determines the appropriate relationship. SP is also responsible for the development of the source primitive VHA HIT Goals, that source is developed during the HISP development and is done in concert with other business owners. SP is also the data steward of the ONC FHIT Strategic Goals within the VHA BAR.

Guidelines

Original

This represents a goal-to-goal relationship of HIT Goals originating from separate government agencies. Relationships will be analyzed and documented at the lowest-level item / node.

History

Original Mapping Performed: May 2018

M15A VA Priorities to VHA BFF

This mapping of VA Top 5 Priorities to the VHA BFF provides the link between the VA Top 5

Priorities to the relevant business functions in the VHA BFF.

Stakeholders

Stakeholders are the BA SP unit and IR (IR did the mappings). The primary stakeholder for this mapped product is SP. The SP team works directly with IR to identify and documents the linkage between each VA Top 5 Priority and the VHA BFF. Mappings were developed by IR and reviewed by S&P.

BA

Guidelines

Original

• Each VA Top 5 Priority aligns to one or more business functions in the VHA BFF.

• For example, the VA Top 5 Priority 1 states that VA is committed to ensure Veterans can make decisions that work best for them and their families.

o This Priority would align with LOB 1, LOB 3, and LOB 4 as it suggests in order for

VA to enable Veterans correct decisions regarding their healthcare, this priority aligns with LOB 1 which is Provide Access to Care, LOB 3 which is Provide

Healthcare Administration as well as parts of LOB 4 which is Deliver Health Care.

More specifically Provide Patient Care Education [4.3.5.1] and Provide Family

Education [4.3.5.2].

History

Original Mapping Performed: May 2018

Typically Updated: As needed

Note: Refer to BAR Release Notes for specific past update dates

M15B VA Priorities to VHA Health IT Goals

Description

This mapping of the VA Top 5 Priorities to the VHA Health IT Goals provides the mapping of the

VA Top 5 Priorities to the VHA Health IT Goals.

Stakeholders

Stakeholder for this mapping is the BA SP unit. The SP team analyzes the contents and premise of the source primitives and determines the appropriate relationship. SP is also responsible for the development of the source primitive VHA HIT Goals, that source is developed during the HISP development and is done in concert with other business owners. SP is also the data steward of the ONC FHIT Strategic Goals within the VHA BAR.

Guidelines

Original

This represents a priority-to-goal relationship of HIT Goals originating from separate government agencies. Relationships will be analyzed and documented at the lowest-level item / node.

BA

History

Original Mapping Performed: May 2018

Typically Updated: Every quarterly

Note: Refer to BAR Release Notes for specific past update datesM16A VHA HIT Goals and

Objectives to Health IT Strategic Drivers

Description

This mapping provides the alignment between the VHA Health IT Goals and Objectives to the

Health IT Strategic Drivers. Both are published in the VHA Health Information Strategic Plan

(HISP).

Stakeholders

Stakeholder for this mapping is the BA SP unit. The SP team analyzes the contents and premise of the source primitives and determines the appropriate relationship. SP is also responsible for the development of the source primitive VHA HIT Goals, that source is developed during the HISP development and is done in concert with other business owners. SP is also the data steward of the ONC FHIT Strategic Goals within the VHA BAR.

Guidelines

Original

This represents a goal-to-goal relationship of HIT Goals and Objectives to Health IT Strategic

Drivers originating from separate government agencies. Relationships will be analyzed and documented at the lowest-level item / node.

History

Original Mapping Performed: October 2018

Typically Updated: As needed

Note: Refer to BAR Release Notes for specific past update dates

M16A VHA HIT Goals and Objectives to Health IT Strategic Drivers

Description

This mapping provides the alignment between the VHA Health IT Goals and Objectives to the

Health IT Strategic Drivers. Both are published in the VHA Health Information Strategic Plan

(HISP).

BA

Stakeholders

Stakeholder for this mapping is the BA SP unit. The SP team analyzes the contents and premise of the source primitives and determines the appropriate relationship. SP is also responsible for the development of the source primitive VHA HIT Goals, that source is developed during the HISP development and is done in concert with other business owners. SP is also the data steward of the ONC FHIT Strategic Goals within the VHA BAR.

Guidelines

Original

This represents a goal-to-goal relationship of HIT Goals and Objectives to Health IT Strategic

Drivers originating from separate government agencies. Relationships will be analyzed and documented at the lowest-level item / node.

History

Original Mapping Performed: October 2018

BA

M16B VHA Health IT Goals and Objectives to VHA BFF

This mapping provides the alignment of the VHA Health IT Goals and Objectives published in the VHA Health Information Strategic Plan (HISP) to the VHA BFF.

Stakeholders

Stakeholders are the BA SP unit and IR (IR did the mappings). The primary stakeholder for this mapped product is SP. The SP team works directly with IR to identify and documents the linkage between each VA Top 5 Priority and the VHA BFF. Mappings were developed by IR and reviewed by S&P.

Guidelines

Original

• All VHA HIT Goals respective Objectives align to one or more business functions in the VHA

BFF.

• For example, the VHA HIT Objective 1.1 branches from VHA HIT Goal 1. Therefore, mapping the business functions to the objective directly maps the BFF to the VHA HIT Goals.

• Map the objectives to the business function within the BFF that closely accomplishes the objectives mission.

History

Original Mapping Performed: October 2018

BA

Topic IV: IT Systems

Topic IV: IT Systems

M18 VA Application List (VASI) to VHA BFF

Description

This mapping of VA Application List (in VASI) to BFF displays a mapping of all IT applications as identified in the VA Systems Inventory (VASI) List to leaf-level functions identified in the VHA Business Function Framework (BFF).

Stakeholders

The primary stakeholders for this mapping are the VA Office of Enterprise Integration (OEI) and the VA Office of Information and Technology (OIT) Office of Enterprise Architecture (OEA). In addition, it is expected that other VHA and VA offices may also utilize information associated with this mapping. This mapping serves as a key component of the VHA Business Architecture.

The VHA Business Architecture team utilizes this mapping as tool in a broad range of analyses and reports that are provided to internal and external stakeholders.

Guidelines

The Business Architecture Integration and Reference (IR) team analyzes the contents and premise of the source primitive (VA Systems Inventory List) and determines the appropriate mapping relationship to the VHA BFF. Specific mapping guidelines are listed below:

• A mapping of a VHA Application (which are contained in the VASI list) to a VHA BFF business function exists when it is determined that the actor/performer of the business function must or may require the services(s) that an application provides at some point during the execution of the business function.

• If the relationship between a VHA Application and business function is limited to provision of information that is developed and/or maintained by the application which serves as a data source that is leveraged in the performance of the business function, this relationship should not be identified as a formal mapping between the VHA Application and the business function.

• If a determination is made that the VHA Application does not have a user interface, i.e., the actor/performer of the business function does not directly interact with the application, then a formal mapping between the VHA Application and the business function should not be established. Applications without user interfaces typically have relationships with other applications. The mappings associated with these types of system-to-system relationships should be developed and maintained by VA OIT.

• A business function will also be mapped to an application if it is determined that any impact to a business function may require modifications to the relating application.

• Only lowest-level item / leaf node business functions will be utilized for system to function mappings in this report. Mappings to parent level functions in the BFF will not be included as part of this report.

BA

Original Mapping Performed: May 2016

The original analysis was performed by the IR unit and continues to be updated by the IR unit bi-annually. The VASI list is updated periodically by the VA OEA team. The IR team routinely monitors the VASI list for modifications and will update the mappings if necessary, however the bi-annual BFF update has routinely been the driver for updating this mapping. At this point in time, VHA business functions are primarily related to VHA-owned applications. The IR is in the process of analyzing non-VHA owned applications for alignment to the VHA BFF.

May 2018 – Expanded mappings to include non-VHA owned applications

The original analysis was performed by the IR unit and only addressed applications that were identified in the VASI as being VHA-owned applications. It was determined that while most if not all health care related applications are VHA-owned, other VHA business functions require or utilize non-VHA owned applications to execute said functions. As a result, IR has mapped all applications in the VASI with a status of “In Development” or “Production” to the VHA BFF.

Applications which are determined to not have a mapping to a VHA Business Function are listed with an entry of “No identified alignment to VHA BFF at this time” in the Business Function

Name column.

April-May 2019 – Internal Review/Validation of Existing VASI System to Function Mappings

A Business Architecture cross-team was formed to review and validate mappings between VHA

BFF business functions and systems identified in the VASI. Current Business Architecture function-system mappings, as well as OEI Business Reference Model (BRM) business function to VASI system mappings were evaluated. All proposed changes were reviewed by the

Business Architecture IR team. These changes helped improve the data integrity of this key

Business Architecture system-function mapping report.

Typically Updated: This report is updated on a continuous basis, whenever updates to BFF or the VASI have been identified.

BA

M19 HIG S&P Solutions Based Architecture to Goals and Priorities

Description

This mapping of the HIG SP Solutions Based Architecture to Goals and Priorities provides alignment between Solutions Based Architectures and the VA Goals and Objectives, VA Top 5

Priorities and VA Strategic Priorities.

Stakeholders

Stakeholders are the BA SP unit and HIG. The primary stakeholder is SP and HIG. The SP team works directly with IR to identify and documents the linkage between each VA Goals and

Objectives and the VHA BFF. Mappings were developed by IR and reviewed by SP.

Guidelines

Original

• Each mapping has its own rationale.

• For example, HIG solution 1 is mapped to VA Top 5 Priority 1 and the rationale for this is that it supports increased access to care through the Choice Program by providing interoperability between the VHA and community providers while preserving security and privacy which leads to improved patient outcomes by applying security classification, sensitivity, integrity, category, and handling instructions markings to healthcare system output prior to access or disclosure..

History

Original Mapping Performed: Map 2018.

M20 Health Information Governance (HIG) Security & Privacy Functional Model

(SPFM) to VHA BFF

Description

This mapping of Health Information Governance (HIG) Security & Privacy Functional Model

(SPFM) to BFF provides a mapping of HIG SPFM to BFF.

Stakeholders

Stakeholders for this mapping are the BA IR and the HIG team. Both units continue to collaborate and be engaged on a yearly basis to address possible updates to the mappings.

BA

Guidelines

Original

A relationship of a Security & Privacy Function to a VHA BFF exists when it is determined that the data at play during the execution of the business function is regulated by an underlying

Security & Privacy Function or mandate. Conversely, a relationship will exist if it is determined that a business function relies upon data that is controlled in some form by the existence of a

Security & Privacy function. Relationships will be analyzed and documented at the lowest-level item/node.

History

Original Mapping Performed: The original analysis was performed collaboratively by the IR and

HIG teams. Routinely, at the beginning of each fiscal year, both units engage with each other to handle any changes to the mapping that may be required based on modifications to the two source primitives. Since the VHA BFF is updated bi-annually, the IR team is responsible for maintaining the mappings mid-year when only the VHA BFF has been modified. The SPFM continues to be modified by the HIG team once a year.

BA

Topic V: VHA Operations

M21A VHA Central Office Organizational Offices Model to VHA BFF

This mapping of VHA Organizational Offices List to VHA BFF displays the mappings from the

VHA Organizations identified in the VA-level Functional Organization Model (FOM) and the latest listing of VHA Program Offices that is posted on the VHA Intranet Site to the VHA BFF.

Stakeholders

None, typically

An exception occurred during an update cycle…