Singapore Healthcare s Journey towards Interoperability, Sharing and Reuse

Transcription

1 Singapore Healthcare s Journey towards Interoperability, Sharing and Reuse Tony Lam*, Senior Consultant Wong Ming Fai*, Senior Consultant Sari McKinnon, Principal Enterprise Architecture Information Systems Division, MOHH 11 th July, 2010 *Also staff of Infocomm Development Authority of Singapore

2 The Crooked Bridge This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 2

3 Outline Introduction MOHH Plan & Key Initiatives Architecture Initiatives Highlight Service Catalogue Interoperability & Integration Architecture National Health Service Bus Reference Architecture Enterprise Architecture Repository Conclusion This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 3

4 Singapore: Small Country but Big City 4.99 million people on sq km (7,025/km 2 ) 125% of Los Angeles population in half its area Ethnically diverse: Chinese: 75 per cent Malays: 14 per cent Indians: 9 per cent 35,000+ healthcare workers 11,580 hospital beds 429,744 hospital admissions (2007) Public sector out-patient visits (2007) Specialist Outpatient Clinics 3,687,910 A&E 752,122 Polyclinics 3,797,953 This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 4

5 Fragmented IT Landscape Primary Care Acute & Intermediate Care Long-Term Care Community Hospital Polyclinics Nursing Home Screening & Preventation Restructured Hospital Palliative Care General Practitioners Rehab & Support Services Home Care Public sector Private sector People sector This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 5

6 One Singaporean, One Health Record Interoperability, Sharing and Re-use are key to: 1.Achieve this vision 2.Maximise Return on Investment This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 6

7 Electronic Records - EMR vs. EHR EMR Specific to an facility (institution, private office); the equivalent of its paper predecessor and includes everything that is recorded by that organization about a given patient. It has depth but lacks breadth. EHR Specific to an individual; captures a key subset of health information from multiple point of service systems. It is available electronically to authorized healthcare providers and the individual anywhere, anytime in support of high quality care. This record is designed to facilitate the sharing of data across the continuum of care, across healthcare delivery organizations and across geographies. This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 7

8 Outline Introduction MOHH Plan and Key Initiatives Architecture Initiatives Highlight Service Catalogue Interoperability Architecture National Health Service Bus Reference Architecture Enterprise Architecture Repository Conclusion This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 8

9 About MOHH Singapore in2015 Goal for Healthcare and Biomedical Sciences This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 9

10 Our Plan Healthcare Innovations Communications, Education and Change Management Patient Care Provider Caregiver Industry Agencies Wellness & Prevention Personal Health Records Primary Care GP IT Enablement Prog* Primary Care Prog * Agency for Integrated Care (AIC) Acute Care Regional Health Services (RHS) ILTC Intermediate (Residential) and Long Term Care Comm (Residential) Hospital Integration Care (CHIC) * National Electronic Health Record (NEHR) Healthcare Informatics Summit 2010 * Intermediate ILTC and Long (Community) Term Care (Community) ILTC Prog & Mental Health Prog * NEHR Prog Joint Healthcare CFC * Telecare Prog * Data Standards Nat l Standards Prog* Medical Product & Service Catalogue Nat l Data Dictionary Nat l Drug Dictionary NEH R EA CIC EA Enterprise Architecture Interop Arch, Services Catalogue NHSB Ref Arch, EA repository Privacy & Security Healthcare Authentication & Access Mgmt Framework Nat l Privacy Framework Medical Informatics Healthcare IT Summit & Medical Informatics Course EHR Clinical Taskforces This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 10

11 Our Plan Healthcare Innovations Communications, Education and Change Management Patient Care Provider Caregiver Industry Agencies Wellness & Prevention Personal Health Records Primary Care GP IT Enablement Prog* Primary Care Prog * Agency for Integrated Care (AIC) Acute Care Regional Health Services (RHS) ILTC (Residential) Comm Hospital Integration Care (CHIC) * National Electronic Health Record (NEHR) Healthcare Informatics Summit 2010 * ILTC (Community) ILTC Prog & Mental Health Prog * NEHR Prog Joint Healthcare CFC * Telecare Prog * Data Standards Nat l Standards Prog* Medical Product & Service Catalogue Nat l Data Dictionary Nat l Drug Dictionary NEH R EA CIC EA Enterprise Architecture Service Catalogue, IIA, ESB Ref Arch, EA Repo Privacy & Security Healthcare Authentication & Access Mgmt Framework Nat l Privacy Framework Medical Informatics Healthcare IT Summit & Medical Informatics Course EHR Clinical Taskforces This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 11

12 Outline Introduction MOHH Plan Architecture Initiatives Highlight Service Catalogue Interoperability Architecture National Health Service Bus Reference Architecture Enterprise Architecture Repository Conclusion This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 12

13 Two Key Dimensions This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 13

14 Two Key Dimensions Interoperability Architecture Service Catalogue National Health Service Bus Reference Architecture Enterprise Architecture Repository This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 14

15 Outline Introduction MOHH Plan Architecture Initiatives Highlight Service Catalogue Interoperability Architecture National Health Service Bus Reference Architecture Enterprise Architecture Repository Conclusion This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 15

16 Service Catalogue Background: Early 2010, two-month effort Objectives: Provide a baseline of NEHR services Take a step towards SOA-based NEHR architecture Deliverables: Approach for identifying services Template for documenting identified services Roadmap for realising services during NEHR implementation This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 16

17 Organisation 5 Domains: EHR, Identify and Access Mgmt, Terminology, National Health Identification Service, Integration x 5 x 24 x 82 x 461 This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 17

18 A Peek into the Service Catalogue DomaFunctional in Area EHR EHR 1. Summary Care Record 1. Summary Care Record Service Name Patient Service Service Name Operation Description Manages the services to register patients. AddPatient DeletePatient Service Operation Description Registers a new patient with the EHR based on inputs from the source systems De Registers the patient from the EHR PID based on the source systems Service Input Patient Particulars; e.g. Last Name, First Name, etc Service Output Success or failure indicator Success or failure indicator This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 18

19 Service Catalogue Construction Approach Develop first-cut based on available information Plan to revise after NEHR vendor selection and finalisation of use cases and requirements First Iteration NEHR Implementation Phase Current Business Requirements COTS Functions/Features Industry Practices Service Modeling Phase 0 SERVICE IDENTIFICATION Service Catalogue v1.0 Finalized NEHR Use Cases Current System Interfaces Service Modeling Phase 1 SERVICE IDENTIFICATION, SPECIFICATION, REALIZATION Service Catalogue v2.0 Existing Catalogue documents Non-Functional Requirements Others This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 19

20 Next Steps Review and update catalogue (leveraging on EA Repository) Get other applications to re-use NEHR services Stronger tie-up with Interoperability Architecture This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 20

21 Outline Introduction MOHH Plan & Key Initiatives Architecture Initiatives Highlight Service Catalogue Interoperability and Integration Architecture National Health Service Bus Reference Architecture Enterprise Architecture Repository Conclusion This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 21

22 Interoperability and Integration Architecture Interoperability Specifications Administration Integration Services Infrastructure Security Key Questions Answered: Interoperability Specifications How can EHR information be understood in a consistent manner? Integration Services What capabilities does the EHR need to provide to support interoperability and integration? Security Administration How does interoperability impact administration and operations of EHR and EMR systems? Infrastructure This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 22

23 Information Exchange Requirements This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 23

24 Linkage to Standards S/ N 5 Doc Request EMRX Name Purpose Integration Standards Request source system for a specific document. Leverages on EMRX s GetDoc functionality. Web Service Semantic Standards EMRX XML This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 24

25 Linkage to Service Catalogue Domain Functional Area Service Name Service Operation EHR 1. Summary Care Record Medication UpdatePatientMedic ation Service Operation Description Update medication(s) on the patient medication list. This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 25

26 Outline Introduction MOHH Plan & Key Initiatives Architecture Initiatives Highlight Service Catalogue Interoperability Architecture National Health Service Bus Reference Architecture Enterprise Architecture Repository Conclusion This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 26

27 National Health Service Bus Reference Architecture Background Most systems integrations (EMR, Labs, Rad etc) in large healthcare settings are using traditional MLLP via integration engine minimal Enterprise Service Bus (ESB) investments to-date. However, ESB is being considered in a number of upcoming large scale healthcare IT initiatives. For example, National Electronic Health Records (NEHR), National Health Identify Services (NHIS), Clinical and EMR Operation System (CLEO) and other hospital cluster wide projects. Opportunity for early alignment!!! This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 27

28 National Health Service Bus Reference Architecture Process One month exercise Over 10 internal/external stakeholders engaged for interviews, major stakeholders participated in working group Deliverables and Outcome A Reference Architecture for ESB landscape Key directions identified for moving towards the reference architecture This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 28

29 Reference Architecture SCM NHG NHG Apps EHR-IX (NHG) Internal SHS EHR-IX (SHS) Internal SHS Apps Other NHG/SHS Cluster (1..n) EHR-IX (Cluster) Internal Cluster Apps EHR-IX (NHG) EHR-IX (SHS) EHR-IX (Cluster) 1 National Healthcare ESB Medinet MOH Apps HPB Apps Characteristics 1. Federated Model. No one single ESB for everybody. Multiple ESB instances in the whole landscape 2. Each hospital cluster will have own physical instance of ESB, with dedicated ESB partition for external integration. 3. Planned initiatives that required ESB capability (e.g. National EHR) 2 MOHH EHR-IX (MOHH) Internal EHR-IX (MOHH) Key Considerations:- Org/structures, governance, operation performance, effort/cost 3 NEHR 3 NHIS CLEOS 3 CHIC 3 AIC 2 EHR-IX (AIC) Internal EHR-IX (AIC) 3 AIC Apps This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 29

30 Key Direction #1 Shared ESB for MOHH driven initiatives Isolated Infrastructure Shared Infrastructure ESB NEHR & NHIS ESB NHG ESB CLEOS Hospital cluster(s) ESB NHG ESB NEHR, NHIS CLEOS, CHIC AIC MOHH driven initiatives ESB ESB AIC CHIC ESB SHS NHG ESB SHS Isolated 1. Investment in more sets of ESB platforms and implementation. 2. Investment in more physical network connections and data centre operations. Shared 1. Investment in less sets of ESB platforms and implementation. 2. Investment in less physical network connections and data centre operations. This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 30

31 Key Direction #2 National EHR to extend the Info exchange platform to support other MOHH initiatives NHG NHG Apps EHR-IX (NHG) Internal EHR-IX (NHG) SHS Medinet EHR-IX (SHS) Internal EHR-IX (SHS) SCM SHS Apps MOH Apps HPB Apps Other NHG/SHS Cluster (1..n) EHR-IX (Cluster) Internal Cluster Apps EHR-IX (Cluster) National Healthcare ESB MOHH EHR-IX (MOHH) Internal EHR-IX (MOHH) NEHR CLEOS NHIS CHIC AIC EHR-IX (AIC) Internal EHR-IX (AIC) AIC Apps Considerations: Scale and project timeline dependency, and infrastructure requirements This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 31

32 Key Direction #3 Leverage on same products/technologies for other ESBs NHG NHG Apps Service Registry EHR-IX (NHG) Internal EHR-IX (NHG) SHS Medinet EHR-IX Registry EHR-IX (SHS) Internal EHR-IX (SHS) MOHH NHG SHS SCM SHS Apps MOH Apps HPB Apps NEHR (Int & Ext) NHIS (Int & Ext) CLEOS (Int & Ext) CHIC (Int & Ext) NHG Apps (Int & Ext) SHS Apps (Int & Ext) Other NHG/SHS Cluster (1..n) EHR-IX (Cluster) Internal Cluster Apps EHR-IX (Cluster) National Healthcare ESB AIC AIC Apps (Int & Ext) Medinet MOH & HPB Apps (Ext) MOHH EHR-IX (MOHH) Internal EHR-IX (MOHH) NEHR CLEOS NHIS CHIC EHR-IX Registry AIC EHR-IX (AIC) Internal AIC Apps EHR-IX (AIC) MOHH NEHR (Int & Ext) NHIS (Int & Ext) CLEOS (Int & Ext) CHIC (Int & Ext) AIC AIC Apps (Int & Ext) NHG NHG Apps (Int & Ext) Medinet MOH & HPB Apps (Ext) SHS SHS Apps (Int & Ext) Considerations Ease of Integration, establishing of logical SOA registry for all cross-org services to facilitate reuse This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 32

33 Outline Introduction MOHH Plan & Key Initiatives Architecture Initiatives Highlight Service Catalogue Interoperability and Integration Architecture National Health Service Bus Reference Architecture Enterprise Architecture Repository Conclusion This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 33

34 1.2.1 Access Screening Data in PHR Access Screening Data in PHR Manage Facility Inf ormation Manage Facility Inf ormation Extract EHR Data for Clinical Audit Extract EHR Data for Clinical Audit Enable EHR Access Manage Patient Enable EHR Access Demographics Manage Capture Care Patient Team Details Demographics Capture Care Team Details Review Summary Record Review Event Details Review Summary Record Review Invest igation Details Review Event Details Review Procedure Details Review Invest igation Details Review Referral Details Review Procedure Details Review Care Plans Review Referral Details Review Notifications Review Care Plans Review Notifications Manage Clinician Inf ormation Manage Clinician Inf ormation Create / Manage Care Plans Reconcile Medications Create / Manage Care Plans Reconcile Problem List Reconcile Medications Update Allergy / ADR Reconcile Problem List Update Allergy / ADR Manage EHR Operations Manage EHR Operations Extract EHR Dat a for Programme Evaluat ion Extract EHR Dat a for Programme Evaluat ion Create / Manage Referral Create Event Summary Create / Manage Referral Create Discharge Summary Create Event Summary Create Discharge Summary Legend Level One business capability Level Two business capability Level One business capability EHR-related functionality Level Two business capability Not directly impacted by EHR EHR-related functionality Not directly impacted by EHR Data Source NHG R1 R R1 - - R R1 R1 - - R1 - - R1 R1 - - R1 - SHS R1 R R1 - - R R1 R1 - - R1 - - R1 R1 - - R1 - GP EMR R Com. Hosp EMR R1 R R R1 R1 R1 R1 R1 R AIC DOT CMIS R NIR R Mindef R R MOH AMD - - R Legend Enterprise Architecture (EA) Repository Background Our IT initiatives involve a lot of integration -> need intensive planning For planning purpose, we gather & generates vast amount of architecture artefacts in differentformats, stored in differentlocations and captured from different perspective. Lack consistent way to maintain/update. Artefacts collected become obsolete overtime Difficult to cross-harmonise and reuse. 1.0 Support & Educate Patient 1.0 Support & Educate Patient 1.1 Educate 1.1 Educate 1.2 Enable Self Management 1.2 Enable Self Management 1.3 Access Care 1.3 Access Care 3.0 Plan & Manage the Health System Plan Manage & Manage the Health 3.2 Manage System Logistics Finances 3.1 Manage 3.2 Manage Logistics Finances 4.0 Manage Population Health 4.0 Manage 4.1 Define Population & Manage Health Performance Targets 4.1 Define & Manage Performance Targets Data Type Patient Demographics Event AMD 2.0 Deliver Health Services 2.0 Deliver 2.1 Schedule Health Services / Register 2.2 Assess Patient 2.3 Deliver Care 2.4 Transfer of Care Care Team 2.1 Schedule / Register 2.2 Assess Patient 2.3 Deliver Care 2.4 Transfer of Care 2.5 Manage Patient Flow 2.5 Manage Patient Flow 3.3 Manage Legal & Commercial 3.3 Manage Legal & Commercial 3.4 Manage HR 3.5 Manage IT 3.4 Manage HR 3.5 Manage IT 4.1 Design Programme 4.2 Execute Programme 4.3 Evaluate Programme 4.1 Design Programme 4.2 Execute Programme 4.3 Evaluate Programme Screening Referral Record Inpatient Disch Sum (str) Com Hosp Disch Sum (str) Polyclinic Evt Sum (str) ED Evt Sum (str) Pvt GP Evt Sum (str) Referral Document Allergies Immunisation Medication Orders History Medications Dispensed History Medications Current Medications Reconciled Problem/Diagnosis History 3.7 Manage Quality 3.7 Manage Quality Problem/Diagnoses Reconciled Lab Orders Lab Reports Rad Report 3.8 Manage Policy 3.8 Manage Policy Rad Orders Rad Image Procedure Report Transfer of Care comp in docs. This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 34

35 1.2.1 Access Screening Data in PHR Access Screening Data in PHR Manage Facility Inf ormation Manage Facility Inf ormation Extract EHR Data for Clinical Audit Extract EHR Data for Clinical Audit Enable EHR Access Manage Patient Enable EHR Access Demographics Manage Capture Care Patient Team Details Demographics Capture Care Team Details Review Summary Record Review Event Details Review Summary Record Review Invest igation Details Review Event Details Review Procedure Details Review Invest igation Details Review Referral Details Review Procedure Details Review Care Plans Review Referral Details Review Notifications Review Care Plans Review Notifications Manage Clinician Inf ormation Manage Clinician Inf ormation Create / Manage Care Plans Reconcile Medications Create / Manage Care Plans Reconcile Problem List Reconcile Medications Update Allergy / ADR Reconcile Problem List Update Allergy / ADR Manage EHR Operations Manage EHR Operations Extract EHR Dat a for Programme Evaluat ion Extract EHR Dat a for Programme Evaluat ion Create / Manage Referral Create Event Summary Create / Manage Referral Create Discharge Summary Create Event Summary Create Discharge Summary Legend Level One business capability Level Two business capability Level One business capability EHR-related functionality Level Two business capability Not directly impacted by EHR EHR-related functionality Not directly impacted by EHR Data Source NHG R1 R R1 - - R R1 R1 - - R1 - - R1 R1 - - R1 - SHS R1 R R1 - - R R1 R1 - - R1 - - R1 R1 - - R1 - GP EMR R Com. Hosp EMR R1 R R R1 R1 R1 R1 R1 R AIC DOT CMIS R NIR R Mindef R R MOH AMD - - R Legend Need for EA Repository Key Challenge: How to maintain, align, exploit and reuse these architecture information for ongoing planning purpose? 1.0 Support & Educate Patient 1.0 Support & Educate Patient 1.1 Educate 1.1 Educate 1.2 Enable Self Management 1.2 Enable Self Management 1.3 Access Care 1.3 Access Care 3.0 Plan & Manage the Health System Plan Manage & Manage the Health 3.2 Manage System Logistics Finances 3.1 Manage 3.2 Manage Logistics Finances 4.0 Manage Population Health 4.0 Manage 4.1 Define Population & Manage Health Performance Targets 4.1 Define & Manage Performance Targets Data Type Patient Demographics Event AMD 2.0 Deliver Health Services 2.0 Deliver 2.1 Schedule Health Services / Register 2.2 Assess Patient 2.3 Deliver Care 2.4 Transfer of Care Care Team 2.1 Schedule / Register 2.2 Assess Patient 2.3 Deliver Care 2.4 Transfer of Care 2.5 Manage Patient Flow 2.5 Manage Patient Flow 3.3 Manage Legal & Commercial 3.3 Manage Legal & Commercial 3.4 Manage HR 3.5 Manage IT 3.4 Manage HR 3.5 Manage IT 4.1 Design Programme 4.2 Execute Programme 4.3 Evaluate Programme 4.1 Design Programme 4.2 Execute Programme 4.3 Evaluate Programme Screening Referral Record Inpatient Disch Sum (str) Com Hosp Disch Sum (str) Polyclinic Evt Sum (str) ED Evt Sum (str) Pvt GP Evt Sum (str) Referral Document Allergies Immunisation Medication Orders History Medications Dispensed History Medications Current Medications Reconciled Problem/Diagnosis History 3.7 Manage 3.8 Manage Policy Quality 3.7 Manage 3.8 Manage Policy Quality Problem/Diagnoses Reconciled Lab Orders Lab Reports Rad Report Rad Orders Rad Image Procedure Report Transfer of Care comp in docs Distilled Info A repositoryis required to capture & manage the gistof the architecture information in a structured manner as a single sourceof info (though may not be the truth) to facilitate ongoing analysis and planning This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 35

36 Example of pain points We need clarity and visibility for the operating environment It is just too complex (e.g. over 150 applications, 300 known interfaces in clinical area alone for just one hospital cluster). Nobody has a full picture. We want to mitigate ambiguity and standardise vocabulary e.g. is it prescribed medications or ordered medications? We want to facilitate Architecture Information Reuse and Sharing e.g. I would like to know roughly which systems process this type of data and who are the project managers that I should talk to formore info. I do not want to start from zero!!! It is a little bit like Knowledge Management!!! This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 36

37 How it is used D Architecture Principles D Architecture Requirements Repository Requirements Constraints Assumptions Gaps Architecture Principles, Vision & Requirements D Architecture Vision Business strategy Business Principles Objectives & Drivers Stakeholders Technology Strategy Business Architecture Application Architecture Data Architecture Technology Architecture A A IT Master Plan(current and to-be view ) supported Business Domains/Organizations (Business Support) - which IT systems provides which Capabilities to which Organizations. A Organization A Capability A Process* (Attachment) Program Plan Planned programs with view of affected Architecture, dependencies and program overlap A A A Application Application Releases A A Component Module Services Information Flow A Business Object (LIM) A Business Data (Physical) A Components A Standard Components A Standard Platform A Glossary Other References D Architecture Decision Log D Staff Contact list D Architecture Position Statement D Deliverable's PARCI D Processes D Toolkits D Specifications? A Typically structured Info that is crucial for architecture planning managed by the EA repository D Typically unstructured info, (e.g. docs) generated for purpose like general communications, consumption by mgmt This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 37

38 Service Catalogue in the EA Repository Service Catalogue Data in the service Applications providing the service This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 38

39 Interoperability Architecture the in EA Repository Interfaces view for a application Interfaces view for a application This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 39

40 EA Repository Supporting Architecture Assurance & Governance Senior Management Stewardship 3 Inner Governance (Internal Operation & Control) Architecture Office Principal Architecture Enterprise Change Architect Management Guidance 4 Architects (Enterprise & Domain) Business Capability 5 Application Status Senior Management 6 EA Project Engagement (Interaction Points) Simplified Interaction 2 1 EA Repository Information Flow Technology Roadmap Implementation Projects (NEHR, CLEO, NHIS) Stage 3 (Delivery) Inception Elaboration Realization 7 New projects to tap on for initial planning Others architecture artefacts 1. EA team member assigned as project architect support a particular project, 2. Identify architecture gaps & opportunities as a natural part of the project execution. E.g.: Shared infra (e.g. ESB) need Reuse existing services 3. Architecture office review gaps and opportunities.. 4. The review will serve as input for ongoing architecture development/ refresh. E.g.: Change in technical standards direction 5. Architecture decision that has cross project/ program impact (e.g. NEHR to extend its ESB to cover others need) will escalate to senior management for support and endorsement. 6. Project architecture info will be refreshed into the EA repository 7. Subsequently, new implementation projects can make use of artifacts in the EA repository (e.g. Current state of applications, IT roadmap etc) for initial planning => avoid starting from zero. This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 40

41 Outline Introduction MOHH Plan & Key Initiatives Architecture Initiatives Highlight Service Catalogue Interoperability & Integration Architecture National Health Service Bus Reference Architecture Enterprise Architecture Repository Conclusion This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 41

42 Conclusion Interoperability Architecture Service Catalogue National Health Service Bus Reference Architecture Enterprise Architecture Repository This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 42

43 Conclusion Singapore is embarking on multiple large-scale, and multi-years initiatives across its healthcare settings, taking an SOA-based approach to facilitate interoperability, sharing and reuse. As of now, key learning points are: Pragmatic how does it help for investment, project planning and implementation? Just-enough & just-in-time effort to show progress and value Continuously to re-visit, re-validate and re-align the architecture to ensure the relevancy Key Challenges are: Diversity of current systems/solution capability, on-going parallel interdependent projects and forever changing landscape This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 43

44 Conclusion If this whole journey is a soccer match, then we are at the end of the pre-match planning. The real match is about to start.. This material contains information that is confidential to MOH Holdings Pte Ltd (MOHH) and should not be circulated beyond MOHH without permission. 44

45 Thank You MOH Holdings