health information blueprint for healthevet brown bag training david reed 28-mar-2006

HEALTH INFORMATION

H E A L T H I N F O R M A T I O N

Blueprint for HealtheVetBrown Bag Training

David Reed

28-Mar-2006

Click to edit Master title style

HEALTH INFORMATION

2

What is it?

Formal definition:A set of diagrams depicting complex views of the organization’s information technology systems architecture, serving as a communication vehicle to put forward information needed across the organization for strategic and technical decision-making to assure optimal systems integration.

Semi-formal definition:An evolving set of community owned diagrams that show the intended realization of the HealtheVet technical vision.

Informal definition:Information to get everyone on the same page regarding technology in order to help us achieve the responsive, nimble system that HealtheVet is intended to be.


HEALTH INFORMATION

3

Who did it?

• Blueprint for HealtheVet Project Team, comprised of Domain Subject Matter Experts (SMEs), Domain Owners, and the Blueprint for HealtheVet Oversight Group, share responsibility for the accuracy, quality, and usability of the Blueprint for HealtheVet publication.

• Principal Authors: Jack Bates, John Beaufait, Dave Bradley, Keith Cox, Susan Dahlberg, Mike Davis, Jim Demetriades, Adriaan Denkers, Satish Gattadahalli, Freida Hall, Donna Harrigan, Galen Mulrooney, Don Oestreicher, Dennis Park, David Reed, Arup Sen, Ioana Singureanu, Steve Wagner.


HEALTH INFORMATION

4

What’s in it?

A1 – Business Function CoverageA2 – Geographic Points of CareA3 – Information Exchange PartnersA4 – Conceptual ArchitectureA5 – Information ProcessingB1 – “As Is” Function to Product

DependencyB2 – Product to Component

DependencyB3 – Enabling Component – Support

Component DependencyB4 – Component Attribute ReferenceB5 – Common Business ServicesB6 – Common Infrastructure ServicesB7 – Inter-Component IntegrationB8 – Component Interactions –

UpdatesB9 – Component Interactions – Reads

C1 – VHA Healthcare Information Model (VHIM) 3.2

D1 – Field Distributed ConfigurationD2 – Centralized Physical

ConfigurationD3 – Telecommunication Physical

InfrastructureD4 – Proposed 2007 Data Center

TopologyE1 – Security Architecture –

Framework and System ViewsE2 – Security Architecture – Developer

ViewE3 – Operational DependabilityF1 – Architectural Standards ProfileF2 – Supplemental Notes


HEALTH INFORMATION

5

What’s its status?

• The Blueprint for HealtheVet went out for peer review in October 2005– Comments were due on 10 November 2005– 152 Issues/Change requests received– 95 Questions/Comments received

• The comments and change requests are being resolved or implemented by the SMEs– On track to complete changes within the next

week or two


HEALTH INFORMATION

6

Where is it?

• Each OI field office should have a draft copy (check with Campus AO)

• Designated peer reviewers received a copy

• Images (at plotter resolution) are available on the Blueprint website: http://vaww.va.gov/vhaea/scripts/blueprintforhev.asp


HEALTH INFORMATION

7

About each sheet

• Each sheet has a descriptive signature block in the lower right corner:

System:

Drawing:

Sheet:

HealtheVet

Product to Component Dependency

U.S. Veterans Health Administration

APPROVAL INITIALS DATE

Chief Health Informatics Officer:

Chief Information Officer:

Program Management Officer:

Direct co-dependencies:

Direct dependencies:Business Functions (A1); Functions to Product mapping (B1)

VHA Chief Architect:

Level of detail:

Domain:

Description:

About this sheet:

Logical

Information

The mapping from high level products (left hand column) to components/services (top row). This sheet will be updated in future releases with better integration of A1 (business functions), the first few B series and the VHA Business Integration Model (VBIM).

Sub-domain: Service decomposition

B200008.00001.20051017

Description

Categorization Sheet Title

“Parent” artifacts“Peer” artifacts

Sheet “Number”

Sheet Unique ID (sheet ID, revision number,

revision date)


HEALTH INFORMATION

8

Sheet references

• Notes and Abbreviations are usually located on the upper right of the sheet

• Legends are usually in the lower left corner of the sheet


HEALTH INFORMATION

9

A1

• A1 depicts the core VHA business functions in a multi-level hierarchy.

• Functions on A1 do not necessarily map directly to any single application or service.

• The sheet will be reconciled with the final version of VA EA 4.1. The sheet is currently in alignment with FEA Health Line of Business Sub-Functions.

• Participant exercise: Consider the items and how they relate to your current project.


HEALTH INFORMATION

10

A2

• A2 depicts the hospitals, clinics, and vet centers where the VHA provides care.

• VA facilities in the Philippines, Puerto Rico and Guam are among the drivers for multi-lingual support.

• Participant exercise: Consider what other ways the breadth of VHA facilities influences HealtheVet.


HEALTH INFORMATION

11

A3

• A3 shows our major information exchange partners along with methods of communication.

• Provides a basic context for understanding the electronic boundaries of the VHA.

• Participant exercise: Consider your project in relation to our boundaries and the impact on HealtheVet.


HEALTH INFORMATION

12

A4

• A4 will show the conceptual architecture.• The current sheet will be replaced.• The current version explores the

architecture from different perspectives:– Within a deployment site as interacting set of

components.– Across the entire VHA as a single unified

system.

• Participant exercise: Consider how you would present the conceptual architecture.


HEALTH INFORMATION

13

A5

• Depicts the flow of information within HealtheVet, including reporting and information analysis.

• The next release will be reconciled with the HIA paper discussing the reporting architecture.

• Participant exercise: Follow the flow of information for both a domain you are familiar with and an unfamiliar one.


HEALTH INFORMATION

14

B1

• Depicts how business functions map to products. The next major version will be less “as is” and more “to be”.

• Possibilities for this sheet include producing a dependency graph from A1 content to B2 content.

• Participant exercise: Consider what functions a random product supports and how many other products support the same function.


HEALTH INFORMATION

15

B2

• Depicts which components enable a given product.

• An enabling component is conceptually a service (an autonomous, self-contained, specialized business function).

• Participant exercise: Consider a random enabling component, what it enables, and what else that product requires. Consider the sequencing impacts.


HEALTH INFORMATION

16

B3

• Depicts what components are required to support the enabling components.

• A supporting component may or may not be a service. In some cases it may be a code library, in others a COTS product, in others basic functions of the runtime environment.

• Participant exercise: Consider how the support components impact the sequencing you considered for B2.


HEALTH INFORMATION

17

B4

• Depicts information about the major components including:– The software environment (OS, programming language,

database)– Physical deployment geography– Hardware environment– Project start and deployment dates

• Participant exercise: Consider a given component, what it enables and how the information presented may impact sequencing.


HEALTH INFORMATION

18

B5

• Depicts the Common Business Services, including SDS and Person Services.

• Because of re-organization, the new version of this sheet may not be completed at the same time as the rest.

• Participant exercise: Consider the different styles of diagram (UML, ERD, box) and whether a single unified style would enhance or hinder ease of understanding.


HEALTH INFORMATION

19

B6

• Depicts the Common Infrastructure Services including Delivery Service

• Because of re-organization, the new version of this sheet may not be completed at the same time as the rest.

• Participant exercise: Consider, for a given HL7 message, what the “on the wire” format might look like and the steps involved in delivering a message.


HEALTH INFORMATION

20

B7

• Depicts (conceptually) how services should access other services (CAIP).

• Participant exercise: Consider the diagrams and supporting text and identify where and how our boundaries (shown on A3) would be affected along with considering how, over time, the approach could benefit internal VHA systems.


HEALTH INFORMATION

21

B8 & B9

• Depict a representative flow through the components in the applied architecture.

• B8 is focused on updates and how updates to information may have to flow to national and then to other sites.

• B9 is focused on reading information.• Both of these need to be reconciled with

forthcoming discussions and decisions about HDR (and by transitivity, CDS).

• Participant exercise: Consider a flow and identify what parts are missing or incorrect.


HEALTH INFORMATION

22

C1

• A tiny excerpt from the VA Health Information Model (VHIM)

• Participant exercise: Consider the relations among entities in the context of your knowledge about information currently in VistA.


HEALTH INFORMATION

23

D1 & D2

• Depict what types of equipment and connectivity may be in the Regional Data Processing Centers and the National Processing Centers for HealtheVet.

• Participant exercise: Consider the diagrams and what impact they might have on HealtheVet deployment options.


HEALTH INFORMATION

24

D3

• Depicts the physical telecommunications infrastructure.

• Note how the backbone has redundant distribution points to each regional WAN.

• Participant exercise: Consider, as a customer of OI&T, how telecom requirements for HealtheVet might be formulated for communication to the service provider.


HEALTH INFORMATION

25

D4

• Depicts the proposed deployment sites (RDPCs) for HealtheVet.

• The Northeast and West coasts are piloting the impacts of collocated VistA systems.

• Participant exercise: Consider how many or what kind of failures would be needed to seriously disrupt HealtheVet.


HEALTH INFORMATION

26

E1 & E2

• Depict the Security Architecture at multiple levels of detail.

• The core of the architecture is an Authentication and Authorization Service.

• Participant exercise: Consider how the levels of detail relate and trace to each other and the impacts of this architecture on HealtheVet code.


HEALTH INFORMATION

27

E3

• Depicts target operational dependability goals and assumptions that are realized by parts of the architecture.

• Participant exercise: Consider a dependability goal and its realizations. From there, consider the practical impact, if any, to the code to be written for HealtheVet.


HEALTH INFORMATION

28

F1

• Depicts the VA EA TRMSP and where those standards will be applied within the HealtheVet architecture.

• Participant exercise: Consider a given standard, where it will be applied within the HealtheVet architecture and what impacts it has on the program (including sequencing) as a whole.


HEALTH INFORMATION

29

F2

• The “notes” page contains:– Information that spans other sheets, including

SMEs responsible for domains depicted in the Blueprint.

– Overarching information that doesn’t fit in any particular domain, including critical quality attributes.

• Participant exercise: Relax after thinking so hard about all the other sheets!


HEALTH INFORMATION

30

What’s next?

• Tech Talk 2006 will feature an Open Spaces session devoted to content authoring and developing plans for the next version and series of the Blueprint.

• Additional content is already planned:– New A4, updated synchronization between A1,

B1, B2, and B3– Finalized critical quality attributes on F2


HEALTH INFORMATION

31

What’s next (cont’d)?

• An “Engineering” Blueprint series is under consideration. These sheets would provide more detail (oriented toward developers) for the actualization of HealtheVet.

• Will be used as a foundational source for external validation of the HealtheVet architecture.

• May be expanded to include more than just “to be” end state.


HEALTH INFORMATION

32

Your feedback

• Please ask questions, provide comments, request changes, or identify issues! The Blueprint will be enriched and sustained by your feedback.– Please use the feedback forms on the Blueprint

website, where you’ll find instructions and info on how input will be handled:

http://vaww.va.gov/vhaea/scripts/blueprintforhev.asp

health information blueprint for healthevet brown bag training david reed 28-mar-2006

Documents

health information blueprint

healthevet publication

component dependency

blueprint website

healthevet technical

healthevet project team

healthevet oversight

product dependency b2