What s What Ahead For Architectures in the DoD? Mr. Dav Da e v DeVr DeV ies Mr. Martin Westphal

Transcription

1 What s Ahead For Architectures in the DoD? Mr Dave DeVries Mr. Dave DeVries Mr. Martin Westphal

2 What Has Happened Organization changes and declining budgets Progress made in Electronic Health Record Data Center Consolidation Revised JCIDS and NR KPP policy Agile IT Acquisition reform Joint Information Environment (JIE) Engagement FMN Framework Warfighter Capabilities Enabling Infrastructure

3 What We Have Heard This Week Secure Information Sharing with Mission Partners Interoperability Data Security Identity Management and Access Management Three Perspectives: (Operator, PfMgmt, Architect) Governance

4 DoD Enterprise Business Warfighting g Intelligence Information Enabling Information Enterprise Architecture Enterprise DoD IEA v2.0 Army DON Air Force Dept of Air Force DIA NGA NRO NSA DLA DISA COC COMS Reference Models OMB FEA DARS Tools DITPR 4 Tech Stds 4 DISR Arch Guidance DODAF Laws, Regs, and Policy Laws Regs Policy

5 Partnering for Success Joint Staff DoD Mission Areas Warfighting Business Intelligence DoD CIO C/S/A IC It s about the Data

6 JC2 Objective Architecture Efforts Data Cloud Redirection Dynamic allocation C2 services integration with ESM Crypto Binding REST Security Further define Info Exchange Patterns Enterprise E2E security services E2E federation of messages Unified approach for mediation Federated Collaboration Widget Framework Cross Domain access control & info exchange (non- DoD partners) Data Cloud Data sync & distribution Federation Caching 6

7 DI2E Architectures Capabilities

8 Architecture Driving Change Mission Requirements & Performance Outcomes Team Business Process Team Presentation Layer Team Systems Capabilities Team Enterprise Architecture Team Data Interoperability Team Common DoD-VA Requirements: HL7 EHR-S Functional Model with DoD and VA vetted Extensions (SV-4) Common DoD-VA Integrated Health Business Reference Model (OV-5) Common DoD-VA To Be Process Flow Model (OV-6C) Pharmacy Presentation (Common GUI) DoD Unique (16) Common (Joint) Applications & (30) VA Unique (6) Battlefield Care Military Readiness Enroute Care Pediatrics Obstetrics Veterinary Disability Evaluation Dental Care Applications and Personal Health Record Inpatient Orders Mgmt Consult & Referral Mgmt Laboratory Emergency Dept Care Immunization Blood Mgmt Document Mgmt Operating Room Mgmt Common o Standards ds Common Standards Common Data Centers Nursing Home Rehabilitative Care Pharmacy Mail Order Common Broker (includes Enterprise Service Bus () and Infrastructure ) Common Information Interoperability Framework (CIIF) Common Information Model, Common Terminology Model, Information Exchange Specifications, Translation Service Common Data Standards: d SNOMED CT and Extensions, LOINC and RxNorm Long Term Care Transient Outreach Occupational Health (VA) Common DoD-VA Measures of Effectiveness, Measures of Performance and Key Performance Parameters Joint DoD/VA DoD Only VA Only 8

9 iehrwf Potential Architecture cmp Clinical Behavioral Health Inpatient Surgery Sevices Outpatient Surgery Primary Care Laboratory Labor and Delivery Pathology Pharmacy Radiology TBI/Behavioral Health Surgery (Inpatient) Surgery (Outpatient) Labor and Delivery Primary Care Laboratory Pathology Pharmacy Radiology Others Mediation Message Mediated Message Routing Enterprise Serv ice Bus Send Message Process Message Translation Send Translated Message Security I/F Infrastructure Registry and Directory I/F Administrativ e Serv ices Clinical Workflow Clinical Communication Security Health Record I&M I/F Registry and Directory Record Patient Assessments Docs Patient Management Preferences History Orders/Refs Instructions Summary Lists Operations Management & Communications Terminology I/F Standard Terminologies and Terminology Workflow Management I/F Health Record Information and Management Serv ices Utiliites Utility Busi ness Rules Management I/F Business Rules Management Serv ices Interoperability I/F Care Management Serv ices MSAT Data HAIMS Data A Health Information Plans Orders Meds Health Main Clinical Decision Support Pop Health Access Analyis Admin/Financial Clinical Support Workflow Management Standards-based Interoperability Medical Situational Awareness Tool HAIMS 9 Common, reusable Infrastructure enables integration of services. to be broken into Clinical, infrastructure, & administrative groupings.

10 Continuing Focus Mature lexicon for architecture development Increase access to Architecture data Revise/update policy and guidance Incorporate architectures into operations, governance and investment decisions Deliver good enough architectures Effectiveness Security Efficiencies

11 Architectures Support JCIDS Process Architectural Artifacts per CJCSI F AV-1 AV-2 CV-2 CV-3 CV-5 CV-6 DIV-2 (OV V-7) DIV-3 (SV V-11) OV-1 OV-2 OV-3 OV-4 OV-5a OV-5b OV-6C C SvcV- SvcV- SvcVor 5 SvcV- SV-1 or S 1 SV-2 or S 2 SV-4 or S 4 SV-5a o SvcV- SV-6 or S 6 ICD 2 X X X X X X X O CDD 2 X X X X X X X X X X X X X X X X 3 3 CPD 2 X X X X X 1 1 X X X X X X X X X X X 3 3 ISP 2 X X X X X 1,4 1,4 X X X X X X X X X X X 3 3 TISP 2 X X X X X 1 1 X X X X X X X X 3 3 StdV-1 (T TV-1) StdV-2 (T TV-2) Legend Note 1 Note 2 Note 3 Note 4 X - Required O - Optional Required only when IT and NSS collects, processes, or uses any shared data or when IT and NSS exposes, consumes or implements shared services. The AV-1 must be registered, and must be public and released at the lowest 22 Total classification DoDAF level Products possible in DARS for compliance. 16 Required 6 Conditional The technical portion of the StdV-1 and StdV-2 are built using DISRonline and must be current for compliance. Not required for JROC approved Operational Requirements Documents. X - Indicates new requirement in CJCSI F More context and understanding earlier in the Capability Development Lifecycle

12 Common Language Warfighter Warfighter Example Example Secure or Seize Clear or Attack in Zone Need Need to Clarify to Clarify Mission Architecture? Joint Mission Threads? Enterprise Architecture? Capability and Requirements? Standards? Mission Architecture? Joint Mission Threads? Command Enterprise Architecture?

13 Summary Its not about the architecture its about the architectural analysis We need to speak Warfighter clearly quantify and articulate the value Much more than materiel solutions Repository/availability of Architectural products and artifacts being developed a team sport Moreimportant in today s environment than More important in today s environment than it ever has been!

14 Questions Mr. Dave DeVries Mr. Martin Westphal

15 BACKUPS

16 Acronyms C2OTM Command and Control (C2) On The Move CBA Capabilities Based Assessment CDD Capability Development Document CPD Capability Production Document DARS Department tof Defense Architecture t Registry System DOD IEA Department of Defense Information Enterprise Architecture DODAF Department of Defense Architecture Framework ICD Initial Capabilities Document ISP Information Support Plan JCIDS Joint Capabilities i Integration and Development System JMT Joint Mission Thread JROC Joint Requirements Oversight Council NR KPP Net Ready Key Performance Parameter TEMP Test and Evaluation Master Plans

17 Joint Information Enterprise End State Coalition Forces Defensibility/Redundancy/Resiliency Federation/Shared Infrastructure Enterprise Identity Access Management Computing Deployed Environment Mission Applications Data Enterprise Information Environment Computing APEX Navy ERP AT21 DCO AFATDS Data Close Combat TM iehr Enterprise Defense Travel Applications Airman Fundamentals Enterprise Information Environment?? 1 7 Home Work Mobile (TDY/Deploy) Access at the Point of Need Future devices